After Pega Cloud Services updates your environment, review the following tasks and complete the tasks that are applicable to your Pega application.

For details about the difference between a major update, a minor update, and a patch, see Pega Platform patches.

• Enabling Admin Studio

  Admin Studio is the portal in which you perform administrative and operations tasks in Pega Platform. To access Admin Studio, grant users either the PegaRULES:SysOpsAdministrator or the PegaRULES:SysOpsObserver role. Admin Studio replaces the System Management Application (SMA).

• Locking and rolling ruleset versions

  If your system includes ruleset names that use ruleset prerequisite validation instead of application-based validation, lock your existing ruleset and roll them into new versions before you continue your development. Locking ensures that future development is based on the updated rulesets and that your applications consistently reference the latest features.

• Identifying conflicts with rules that cannot be overridden by running the final rules conflict report

  The Final Rules Conflict Report lists rules in your system that reference final Pega rules for this release. These rules vary depending on the specific release from which you are updating.

• Updating from Pega Survey 7.2.2 or earlier: enabling the new Pega Survey features

  For applications using Pega Survey, if you are updating from Pega 7.2.2 or earlier, update your application to use the latest survey features.

• Updating from Pega Platform version 7.2.2 or earlier: enabling notifications by updating access role names

  When updating from any release prior to Pega 7.2.2, you must update all the user access role names of an application with specific classes so that users can receive notifications.

• Updating from Pega Platform version 7.2.2 or earlier: enabling access to environmental information

  Enable access to environmental information to avoid an apparent flaw in some security audits.

• Optional: Enabling new UI kit and Cosmos features

  To take advantage of the latest user interface elements, including templates and icons, add the latest version of the UI Kit or Theme-Cosmos application to the Built On Applications List. You can still continue to use your current version of the UI Kit or Theme-Cosmos to avoid additional post-update steps, but then you will not have access to the latest features, functions, and fixes.

• Running update utilities

  Pega Platform includes several update utilities to help you to update your application to use new features. Run all of the update utilities.

• Updating your applications

  If you did not run the Update Existing Application utility during the update, you can run it after the update to ensure that your existing applications take advantage of new functionality in Pega Platform. Run the utility first on your development system and test the changes. Then, run the utility again on the production system. The specific actions required for your application depend on your current version.

• Updating from Pega Platform version 7.3, 7.3.1, or 7.4: granting access to the Requester Management landing page

  To access the Requester Management landing page in your application, add privileges to the @baseclass and Pega-Landing access classes in your access roles.

• Reviewing and updating agent associations using node type

  In Pega Platform 7.3 and later, all nodes in Pega Cloud Services environments support associating agents with node types. With node classification, agents no longer create or utilize NodeID-based Data-Agent-Queue (DAQ) instances. After Pega Cloud Services finishes updating your environment, agents are mapped to the BackgroundProcessing node type by default; previously configured DAQ customizations using NodeId are removed.

• Updating from Pega Platform version 7.3 or earlier: Updating service email rules to reply to Pulse email notifications

  If you configured service email rules in Pega Platform 7.3 or earlier, following an update, you must add required fields in order for your applications to reply to Pulse email notifications correctly.

• Reverting customized log-in page

  If you see the log-in page for the previous version of Pega Platform the access group might have reverted to the default access group after the update. To display your customized log-in page, reset the access group.

• Reviewing the content storage location

  For Pega Platform 7.4, the default content storage location changed from Pega database to Pega Cloud File Storage.

• Performing post-update steps in your Pega applications

  Review required post-update steps in your Pega applications.

• Testing your applications

  After your update, perform regression testing to verify that application functionality works as expected. As part of regression testing, perform smoke testing to verify that critical functionality works as expected. To instantly ensure that specific functionality works appropriately, run sanity tests.