Skip to main content


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

Automatically update dependent applications to be built on the latest application versions in an archive (8.5)

Updated on May 3, 2021

When you import a product archive, you can now automatically update dependent applications to be built on the latest versions of the dependent applications that you select. By automatically updating dependent applications, you save time and reduce the errors that can occur when you manually update applications to use new built-on application versions.

For example, if you are creating a product archive from the HR Services app, which contains MyDemoApp and Applicat, you can specify that you want to update dependent applications for MyDemoApp and Applicat on the HR Services Product rule form, as shown in the following figure:

"Updating dependent applications on the Product rule form"
Updating dependent applications on the Product rule form

 If there are newer versions of the Applicat and MyDemoApp applications than those that are on the server, when you import the archive, you can use advanced mode to view the latest versions of those applications.You can then select the applications for which you want to update dependent applications, as shown in the following figure:

"Viewing and selecting the latest built-on application versions"
Viewing and selecting the latest built-on application versions

 Applications that are built on earlier versions of Applicat and MyDemoApp are automatically updated to be built on the latest versions after you import the archive, as shown in the following figure for the My new app application:

"Application automatically updated to use new built-on application versions"
Application automatically updated to use new built-on application versions

For more information, see Updating dependent applications with the latest versions of built-on applications.

  • Previous topic Identify job scheduler activities that exceed the run time threshold (8.6)
  • Next topic Identify performance issues with queue processor and job scheduler activities (8.5)

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us