Checking Out Non-latest Objects
You may want to revert to an earlier version of a CAD or dynamic document (the only object types currently supported for this functionality). You can use the Version History of the latest iteration of the object to identify an earlier iteration, navigate to its information page and initiate a checkout. In general, you can initiate the checkout of a non-latest iteration from the same places you would initiate the checkout of the latest iteration. Exceptions are the row-level check-out actions available in places such as the workspace page, the workspace Edit Properties page, and the Check In page.
Check out of a non-latest of an object is supported, subject to the following conditions:
• A context-level preference is set to allow checking out non-latest objects. This preference may be set to allow checking out without the conflict message mentioned later in this topic. For more information, see the section
Creo Parametric – Windchill Integration.
• You receive a warning that the iteration you are attempting to check out is not the latest.
• If you perform the checkout using the Check Out and Add to Workspace page, a conflict message saying an iteration other than the latest cannot be checked out is displayed in the Event Management utility. This is an overridable conflict that can be overridden using the Conflict Management utility.
• No other iteration of the object can be currently checked out. Also, when you check out a non-latest iteration, all other iterations of the object are adorned with a "checked-out" symbol. The symbol indicates that no other iterations can be simultaneously checked-out. (In the Version History table, to avoid confusion, only the iteration actually checked out displays the checked-out symbol.)
• When gathering related objects of an initially-selected object that is not the latest iteration, the default configuration is the As Stored configuration for the initially selected object (not Latest). This can be modified by the Windchill preference: Set Configuration for Check Out.
• Upon checking the object back in, it becomes the latest iteration. The Version History table records the earlier iteration it was derived from.
• When checked out, the object has both the content (only if a CAD document) and meta data of the earlier iteration. When checked in, however, the earlier iteration is assigned the life cycle state of the iteration that had previously been the latest.
• Checking out an earlier iteration from a project to a workspace is allowed, so long as:
◦ The version is native to project, or is checked out to the project.
◦ The object is not checked-out by any individual.
◦ The version is not shared to the project from Windchill PDMLink.
• Association between objects can be affected when checking in a non-latest iteration to become the latest, as follows:
◦ Uses link—Links between parent and children in a structure are maintained.
◦ Content link—If a part and CAD document associated by a content link are iterated (checked in) separately, the new iteration retains the association to the peer object it was originally associated with. If the part and CAD document are both iterated, then a new content link is formed between the two peer objects.
◦ Owner link—If a CAD document is iterated, its peer part (one associated by an owner link) is also iterated by the system.