Skip to main content

Published Release Notes

Find release notes for the selected Pega Version and Capability

Browse resolved issues for Platform releases.

This documentation is for non-current versions of Pega Platform. For current release notes, go here.

Improved creation of When rules with the condition builder

Valid from Pega Version 8.3

Define conditions for When rules by using the condition builder view. You can create new or select existing values, and then group conditions with ANDs, ORs, or advanced logic. The condition builder does not support functions; the method for defining the conditions to use functions is the same as in the previous versions of Pega Platform™. 

For more information, see Defining conditions with a condition builderDefining conditions for a When rule.

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).

Support for controlling simulations in Integration Designer

Valid from Pega Version 8.3

Integration Designer now supports toggling an existing simulation for a data source on and off, and supports creating a simulation when a data source does not have a simulation configured. By simulating a data source, you can continue developing an application when your integration is not available, and test an application independently from the integration.

For more information, see Managing data and integrations with the Integration Designer.

Support for additional key management services

Valid from Pega Version 8.3

By supporting additional key management services, Pega Platform™ offers you increased flexibility when defining keys that are used for encryption of application and internal system data. You can now create keystores that reference keys from key management services such as Microsoft Azure Key Vault, HashiCorp Vault, and Google Cloud KMS, in addition to Amazon KMS. You can also create a keystore that references other key management services through the use of a data page.

For more information, see Configuring a Microsoft Azure Key Vault keystore, Configuring a HashiCorp Vault keystore, and Configuring a Google Cloud KMS keystore.

Automatically generate OpenAPI Specification documentation for application REST APIs

Valid from Pega Version 8.3

You can now access a clear, standard view of all the REST APIs in your application by using autogenerated OpenAPI Specification (OAS) documentation. In App Studio, you can view the OAS documentation generated for application-specific REST APIs by using the new Application tab in the API channel. Additionally, service package rules now include an OpenAPI tab where you can view the automatically generated OAS documentation for all the REST services included in the service package. With these enhancements, you can easily find, visualize, and test the REST APIs in your application.

For more information, see Generating OpenAPI Specification documentation for application-specific REST APIs.

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.

Ensure event strategy reliability through unit tests

Valid from Pega Version 8.3

You can now automate event strategy testing and increase the reliability of the event strategy configuration through unit tests. Avoid errors and ensure that the strategy delivers the expected results by configuring assertions on property values, aggregates, and result counts.

For more information, see Increased event strategy reliability through unit testing.

Data migration enhancements

Valid from Pega Version 8.3

Ensure a successful data migration by using a configuration template for setting up your environment before you migrate data into your application. From the new Migration settings landing page, configure dynamic system settings for migration and turn off database indexes and processes that might affect data migration performance. After you have finished migrating data, you can revert your system to its normal working state.

For more information, see Creating a migration configuration template.

Ability to import and export Intelligent Virtual Assistant or Email Bot training data

Valid from Pega Version 8.3

You can now copy Pega Intelligent Virtual Assistant™ (IVA) or Pega Email Bot™ training data between Pega Platform™ application environments by performing an export and import action. Importing and exporting training data between Pega Platform application environments results in greater accuracy of entity detection. Entities are detected by the system in a chat conversation, including attachments, to help respond to the user correctly, and consist of proper nouns that fall into a commonly understood category such as a person, organization, or a ZIP code. The ability to copy training data also makes it easier to maintain IVA or Email Bot, and build its artificial intelligence.

For more information, see Copying training data to another environment and Copy training data and model to another IVA or Email Bot environment.

Visual Data Model enhancements

Valid from Pega Version 8.3

View your application's full data model, see how its entities are related, edit and delete fields, and add fields to the model without exiting the Visual Data Model. In addition, you can now search the entire data model for fields and select a case or data type class to see its fields and relationships.

For more information, see Exploring the data model.

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