Automatic management of run-time context for background processing
Valid from Pega Version 8.3
Management of system run-time context is now automatic. You no longer need to manually modify the AsyncProcessor requestor type context to make a queue processor or job scheduler work after importing or upgrading an application. Additionally, you do not need to manually modify the AsyncProcessor requestor type context to make new queue processors and job schedulers work.
For more information, see System general landing page and Automating the runtime context management of background processes.
Upgrade impact
After upgrade, you manage the runtime context of your background processing in System Runtime Context instead of in the deprecated AsyncProcessor requestor type.
What steps are required to update the application to be compatible with this change?
Select the Include in background processing option in the Advanced section of the application rule form for all applications that use background processing (such as Job Schedulers and Queue Processing). When this option is enabled, the system automatically includes the rulesets (for the application and its components) in System Runtime Context used for resolving and running Queue Processors and Job Schedulers. Also, when the option is enabled, the application is placed on the System Runtime Context list during application rule saves (such as during application import and migration).
Define a default reporting database
Valid from Pega Version 8.3
You can now easily define a reporting database for all classes that are assigned to a primary database. You can also assign this reporting database as the default reporting database. This provides support for reporting against Amazon Aurora read replicas. AWS Aurora increases the performance and stability of your database management system.
For more information about reporting, see Report Definition data access tab.