Integrations (PTC products, 3rd party products and code) > 3rd party product integrations (CM, DOORS, Rose, Simulink and XML) > Configuration management tool integration > Typical lifecycle of a model stored in a CM tool (CM tool integration) > Sub-package options for get latest and check out operations (CM tool integration)
  
Sub-package options for get latest and check out operations (CM tool integration)
When you perform a get latest or check out operation on a Package, you can choose to get/check out sub-Packages and get/check out new Packages.
Effect of sub-package options on get latest operations
When you perform a get latest operation, you can choose to get sub-Packages and get new Packages.
If you do not get sub-Packages and do not get new Packages, the get latest operation is performed only on the Package or Model you selected.
If you get sub-Packages, but do not get new Packages, the get latest operation is performed on the following items:
The Package or Model you selected.
All descendent Packages that exist in the Modeler environment.
If you get sub-Packages and get new Packages, the get latest operation is performed on the following items:
The Package or Model you selected.
All descendent Packages that exist in the Modeler environment.
All descendent Packages that exist in the CM tool environment.
Example - get latest operations
In the following example, a get latest operation is performed on Package A, Package J is unchanged, and Package K is created as a Stub to maintain the Package hierarchy of Package A.
In the following example, Package A is updated. The Get Sub-packages option results in any Modeler sub-Packages being updated, in this case Package J. Package K is created as a stub to maintain the Package hierarchy of Package A.
In the following example, Package A is updated. The Get Sub-packages option results in Package J being updated. The Get New Packages option results in a get latest operation performed on Packages K, W and X.
Effect of sub-package options on check out operations
When you check out a Package, you can choose to check out sub-Packages and check out new Packages.
If you do not check out sub-Packages and do not check out new Packages, the check out operation is performed only on the Package or Model you selected.
If you check out sub-Packages, but do not check out new Packages, the check out operation is performed on the following items:
The Package or Model you selected.
All descendent Packages that exist in the Modeler environment.
If you check out sub-Packages and check out new Packages, the check out operation is performed on the following items:
The Package or Model you selected.
All descendent Packages that exist in the Modeler environment.
All descendent Packages that exist in the CM tool environment.
Example - check out operations
In the following example, Package A is checked out, Package J is unchanged, and Package K is created as a Stub to maintain the Package hierarchy of Package A.
In the following example, Package A is checked out. The Checkout sub-Packages option results in any Modeler sub-Packages being checked out, in this case Package J. Package K is created as a stub to maintain the Package hierarchy of Package A.
In the following example, Package A is checked out. The Checkout Sub-packages option results in Package J being checked out. The Checkout New Packages option results in a check out operation performed on Packages K, W and X.