Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Manage aged application updates in Deployment Manager

Updated on May 3, 2021

Beginning in Deployment Manager 4.x, can now manage aged application updates. An aged update is a rule or data instance in an application package that is older than an instance that is on a system to which you want to deploy the application package. By being able to import aged updates, skip the import, or manually deploy the application package on a system, you now have more flexibility in determining the rules that you want in your application and how you want to deploy them.

For example, you could update a Dynamic System Setting on the quality assurance system, which has an application package that contains the older instance of the Dynamic System Setting. Before Deployment Manager deploys the package, the system detects that there is a newer version of the Dynamic System Setting on the system than in the package and creates a manual step in the pipeline. From this step, you can select if you want to import the aged update that is in the package into the system to override the newer Dynamic System Setting instance or if you want to skip the import. You can also choose to skip the manual step and then use the Import Wizard to manually deploy the package.


Deployment Manager aged updates options

For more information, see Using Deployment Manager 4.1.x.

  • Previous topic Deploy with confidence by enforcing quality metrics
  • Next topic Diagnose pipelines and view troubleshooting information

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us