Move Restrictions

• To move an object from one folder to another in the same context or in two different contexts, you must have the appropriate permissions in both the source and destination folders and on the objects in those folders. For more information on permissions, see your system administrator.

• When moving only the current versions of an object, the object cannot be moved across contexts. The move must be within the same product or library. If you move all version of an object, the object can move to a different product or library.

• Objects cannot be moved if they are checked out, even if the user attempting to move them is the same user who has the objects checked out.

◦ If an object in a folder you are moving has several versions located in different folders, all of those versions will be moved with the folder to the target location. If, however, all the folders containing different versions of the object are moved at the same time, the different versions will remain associated to their respective folders.

◦ If an object has several revisions located in more than two folders, and not all folders are moved, an overridable conflict will appear. You will be directed to accept that the object versions that are not included will be moved to the folder of the lowest version being moved.

• When versions of an object are moved from one context to another, the versioning scheme for those versions will not change. The history of the object and all of its versions and iterations are preserved during the Move action.

• A versioning scheme defines the labels, or identifiers, that are automatically applied when object versions are created. For example, the versioning scheme determines whether the version identifiers are integers, alphabetic characters, or some combination of both integers and characters.

• If your site displays folder domains, note that when you move an object iteration to a folder with a different domain, all iterations of the version are reassigned to the domain associated with the destination folder. A domain is an administrative area that defines a set of administrative policies, such as access control, indexing, and notification. Folders associated with a domain are subject to its policies.

• When an object version is moved from one context to another, the team associated with the object version will be moved as well, provided that the template used to create the team is managed at an organization or site level. If the team template is managed at a product or library level, then the object cannot be moved to a different product or library, and you will receive a non-overridable conflict when you attempt to move it. When an object that has been moved is revised, then the new version is assigned a team based on the policies and rules for the context.