Published Release Notes

Platform truststore for validating certificates

Pega Platform™ now includes a platform truststore, to which you can import X.509 certificates that are common across platform applications. When a certificate needs to be validated, Pega Platform looks for the certificate at the connector level, then in the platform truststore, and finally in the application server (JVM) truststore. You can add, update, and delete certificates in the platform truststore without having to restart the server, which is useful when TLS certificates are changed for reasons such as key rotation.

For more information, see Importing an X.509 certificate.

Test coverage support for more rule types

Test coverage has been expanded to include the following rule types. Test coverage support for these rule types enables developers to more accurately measure the effectiveness of their tests.

• Collection
• Declare trigger
• Map value
• Navigation 
• Report definition
• Scorecard

For more information about test coverage, see Test coverage.

Upgrade impact

The new rule types may impact the test coverage metrics for your applications. Due to the increased number of supported rules, the reported test coverage percentage will decrease.

What steps are required to update the application to be compatible with this change?

Run your coverage reports after upgrading to see the latest metrics.

Swipe actions in repeating dynamic layouts in a mobile app

Lists that are based on repeating dynamic layouts now support swipe actions. The menu of available actions, such as Edit or Delete, does not obscure the view and is displayed only when a mobile app user swipes a row. Users benefit from easier navigation and they can do smaller tasks quickly, without leaving the main screen.

For more information, see Configuring swipe actions for a mobile app.

Web mashups preview

App Studio now has a preview mode that shows how an integrated Pega application is displayed on a chosen website. You can try different host sites, as well as window sizing types and skins, to find the best presentation options.

For more information, see Creating a mashup demo.

Numbered accordion for layout groups

Layout groups and dynamic layout groups with the accordion layout now support automatic numbering of collapsible headers. You can now build better user forms, as the numbers show the steps that users need to follow to fill out a form so that they know the process stage at every moment. Automatic numbering accommodates when conditions that are used in accordion sections.

For more information, see Creating a layout group.

Stream-based alternative for interaction history

Accelerate the processing of high-volume interaction history data by incorporating a stream-based interaction history into your application. A stream-based interaction history processes large volumes of data more quickly than a traditional relational database interaction history so that you can react to your customers' needs in real time.

For more information, see Process high-volume interactions more efficiently and Aggregates-only mode for a stream-based interaction history.

Aggregates-only mode for a stream-based interaction history

Activate the aggregates-only mode to efficiently transition your application from a relational database interaction history to a stream-based interaction history. By transitioning from a traditional relational database interaction history to a stream-based interaction history, you enable your application to process large volumes of data more quickly so that you can react to your customers' needs in real time.

For more information, see Transitioning to a stream-based interaction history.

Improved performance for work ID generation

Work IDs are now generated in batches and managed with dynamic system settings. Batch-based ID generation improves performance and scalability, which reduces the time that it takes to migrate data to a Pega Platform™ application.

For more information, see Default dynamic system settings data instances.

Upgrade impact

In a multi-node environment, the new ID generation method can assign IDs that are not as sequential as in the previous method.

For example, in a 2-node cluster, the IDs could come in from each node in batches of 1000, resulting in successive Work objects having IDs that differ by 1000 (such as 1, 1001, 2,1002, 3, 1003). As more Work objects are created the gaps can get filled. However, there might still be gaps left in the generated IDs.  For example, if a node crashes or shuts down, some IDs would be missing, or if a node has given out 600 IDs from a batch of 1000 IDs, then 400 IDs would remain unused. In most situations, this should not be an issue. 

What steps are required to update the application to be compatible with this change?

If you must have nearly sequential IDs or cannot accept gaps in IDs (and do not need the performance improvement), then you can change the dynamic system setting to disable the new ID generation method. 

The dynamic system setting for this feature is idGenerator/defaultBatchSize. The feature is enabled by default with a defaultBatchSize of 1000. To disable the feature, set the value to 1.

Improved control of case locking and retry mechanisms

The Delay factor, Initial delay in minutes, and Max retry attempts fields have been added to queue processors, and the Timeout to acquire lock field has been added to the Queue-For-Processing method. Using these fields, you can quickly configure background processes that require you to lock cases or retry case processing.

For more information, see Creating a Queue Processor rule.

Upgrade impact

After a successful upgrade, the new fields contain their default values.

What steps are required to update the application to be compatible with this change?

To customize the functionality of this feature (and the new fields), open the Queue-For-Processing definition and modify the values for the new properties or fields.

Improved creation of When rules with the condition builder

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 builder, Defining conditions for a When rule.