Add or Modify Package Dependencies
A package dependency allows you to specify dependencies that must be in place for proper deployment of a package. The Add or Modify Dependencies page allows you to perform the following tasks:
• Specify package dependencies when creating a package.
• View or update dependencies on existing unpublished packages.
• View package dependencies for a published package.
 |
You can add or modify a package dependency only for unpublished packages. After publishing a package, you can no longer add, edit, or delete a dependency. You can make a copy of the package and update its dependencies.
|
Complete the following steps to add dependencies to a package:
1. From the left pane in ThingWorx Software Content Management, under the Packages section, navigate to > .
The Add or Modify Dependencies page appears.
2. Click on theDependency Type.drop-down to select a package dependency type, either Version or Property. The default is Version.
3. Ensure that the package that you want to add dependencies to is displayed in the Selected Package field.
This field displays the last package that was created or the last package that was selected. If you want to add dependencies to a different package, click 
, and select the correct package from the Find Packages page.
, and select the correct package from the Find Packages page.4. In the Package Name field, enter the name of the package that you want to add as a dependency.
| | Older packages that have letters as the version cannot be added as a package dependency. |
5. In the Version to Depend On field, enter the version of the package that you entered in step 4.
The Version to Depend On specifies the version that your package relies on to be eligible for deployment.
Alternatively, click 
to display the Find Packages page. You can then add an existing package that populates the Package Name and Version to Depend On fields automatically.
to display the Find Packages page. You can then add an existing package that populates the Package Name and Version to Depend On fields automatically.6. In the Operator list, select one of the following options:
◦ >—Specifies that the version of the selected package must be greater than the specified version.
◦ <—Specifies that the version of the selected package must be less than the specified version.
◦ >=—Specifies that the version of the selected package must be greater than or equal to the specified version.
◦ <=—Specifies that the version of the selected package must be less than or equal to the specified version.
◦ ==—Specifies that the version of the selected package must be equal to the specified version.
◦ !=—Specifies that the version of the selected package must not be equal to the specified version.
◦ *—Specifies that any version of the selected package is acceptable.
7. Click 
to add the package as a dependency.
to add the package as a dependency.| | You have to save the package dependency as mentioned in Step 14. |
| | If you add a package that is not available in the ThingWorx Software Content Management utility, the package is highlighted in yellow in the Dependencies table. |
8. In the Dependencies table, review the details, and if required, perform the following actions:
◦ Select a dependency and click 
to modify a package dependency:
to modify a package dependency:a. In the Package Name field, type the name of the package.
b. In the Operator list, select the appropriate operator.
c. In the Version to Depend On field, type the correct version of the package that you entered.
d. Click Save to update the package dependency. Alternatively, click Cancel if you do not want to modify this package dependency.
◦ Select a dependency, and click 
to delete a package dependency.
to delete a package dependency.If you selected Property as a dependency type in Step 2 perform the following steps:
9. In the Property Name field, type the name of the property that you want to add as a dependency.
10. In the Property Value field, type the value for the property that you entered in step 9.
The Property Value specifies the value that your property relies on to be eligible for deployment.
Alternatively, click to display the Find Properties page. You can then add an existing property that populates the Property Namefield automatically.
to display the Find Properties page. You can then add an existing property that populates the Property Namefield automatically.11. In the Operator list, select one of the options as in Step 6.
12. Click to add the property as a dependency.
to add the property as a dependency.| | You have to save the package dependency as mentioned in Step 14. |
13. In the Dependencies table, review the details, and if required, perform the following actions:
◦ Select a dependency, and click to modify a property dependency:
to modify a property dependency:a. In the Property Name field, type the name of the property.
b. In the Operator list, select the appropriate operator.
c. In the Property Value field, type the correct value of the property that you entered.
d. Click Save to update the package dependency. Alternatively, click Cancel if you do not want to modify this package dependency.
◦ Select a dependency, and click to delete a package dependency.
to delete a package dependency.| | Property dependencies enable you to set the condition for the package deployment based on a requirement that a local or remote property be of a certain value or within a certain range. To learn more about dependencies see: Set Conditions For Property Dependencies For a list of possible error messages when using a property dependency see: Error Messages for the Version or Property Dependency |
14. After you have added the Version or the Property as a dependency: Click Save.
Click Clear to delete all the dependencies that are available in the Dependencies table.