Task action resolution in Deployment Manager

An aged update is a rule or data instance in an application package that is older than an instance on a system to which you want to deploy the application package. By importing aged updates, skipping the import, or manually deploying your application changes, you have flexibility in determining the rules that are required and how they must be deployed.

When an aged update is encountered, the deployment waits for a user action. If the user has the Manage aged updates privilege, they can manage aged updates in multiple ways, such as importing the update, skipping the import, or manually deploying applications.

For more information about how to manage aged updates, see Managing aged updates.

Check your knowledge with the following interaction:

Suppose an application package that is set for deployment on candidate systems contains schema changes. In that case, the Pega Platform™ orchestration server checks the candidate system to check whether the user has the required system privileges to deploy the schema changes.

One of the following results occurs after the server checks the candidate system:

• The schema changes are automatically applied to the candidate system if the user has the appropriate privileges and the application package is deployed to the candidate system. The deployment does not generate any alerts if the schema changes exist in an artifact.
• If the user does not have the appropriate privileges, Deployment Manager generates an SQL file that lists the schema changes and sends the file to the email address of the user. The deployment pauses for manual input so that the user can apply the schema changes. After the user completes the step, the user confirms the same on the deployment. If the user selects the option to deploy manually and resume, the deployment resumes from the next step.

For more information about how to automatically deploy schema changes, see Configuring automatic schema changes.

Check your knowledge with the following interaction.