After you update Pega Platform, update your application and schema, identify and resolve potential conflicts, and validate the update. As a best practice, run all of the update utilities.

• Running the Update Existing Applications utility

  To automatically make your existing applications compatible with the new version of Pega Platform, use the Update Existing Applications utility.

• Identifying rule conflicts

  To identify potential conflicts between custom rules in your application and the updated version of Pega Platform, run the Final Conflicts report.

• Identifying missing database tables

  To confirm that all the required database tables in the Pega Platform base schema are present in your system after an update, view the Update Applications Schema tab.

• Updating cases and followers

  You can run a utility in your application to update the cases that users were following in previous releases so that the cases are no longer locked when they are followed. By using this utility, other users can follow cases, because they are no longer locked.

• Updating cloned tables after an update

  To apply the schema changes in the latest base tables to the cloned rule, data, work, and history tables during or after an update, use the Update Applications Schema utility. Applying the changes enables updated reports on those tables and improves performance.

• Updating Get Next Work performance

  To improve the performance of Get Next Work in querying assignments that were created in prior versions of Pega Platform, run the Skill count update for assignments utility.

• Finding deprecated rules in sections

  Find sections that use deprecated rules by using an application update utility. Once found, these legacy rules can be updated to newer rules.