Windchill Fundamentals > Working with Windchill Objects > Actions Common Among Objects > About Move
About Move
The Move action allows you to move specific objects between contexts and to specify different locations for each object.
The Move action is similar to cut and paste. However, while the cut and paste actions are useful for moving one version of an object within a context, the Move action provides the option to move all versions of the selected objects, all view versions, or just the current version and related iterations of the object.
If you move all versions of selected objects, they can move between:
A product and library
Folders in a single context
If you move all view versions or just the current version and iterations, the move must be within the same product or library.
The Move action is not available for projects or programs.
There are additional restrictions on the Move action. For more information, see Move Restrictions.
The Move action also provides dependency processing, allowing you to gather other related objects to move as well. Related change objects maintain their associations with the object when it is moved.
If the object you are moving has associated objects such as representations, effectivity statements, discussion topics, or baselines, then those objects are automatically moved as well.
When an object is moved from one context to another, its name and number does not change. Any running processes associated with the object version that you are moving are also moved with the version as long as the templates used to create these processes are managed at an organization or site level. These processes include:
Associated workflow processes
Life cycle
Access control
You can move an object at any time, but it is best to move it when its latest version is released. This ensures that new versions are assigned a team and life cycle based on the initialization rules set for that context.
It is best to use the same life cycle for the same object type within an organization. This prevents life cycle inconsistencies between contexts.
When the moved object is revised, the new version is assigned new processes, including a team, workflow, life cycle, and access controls. These processes might change, as they are subject to the policies or rules for the context in which the object is now managed. (For example, the access control policies might be different in the new location; therefore, the access control policies for the object would change.) For more information, contact your system administrator.