Skip to main content

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

Managing aged updates

Updated on December 13, 2021

You can manage aged updates in a number of ways such as importing them, skipping the import, or manually deploying applications. Managing aged updates gives you more flexibility in how you deploy application changes.

Do the following steps::
  1. In the Designer Studio footer, click Deployment Manager.
  2. Click the pipeline.
  3. Click View aged updates to view a list of the rules and data instances, which are in the application package, that are older than the instances that are on the system.
  4. Click the More icon and do one of the following actions:
    • To import the older rule and data instances that are in the application package into the system, which overwrites the newer versions that are on the system, click Overwrite aged updates.
    • To skip the import, click Skip aged updates.
    • To manually deploy the package from the Import wizard on the system, click Deploy manually and resume. Deployment Manager does not run the Deploy step on the stage.
  • Understanding aged 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 your application changes, you now have more flexibility in determining the rules that you want in your application and how you want to deploy them.

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