Published Release Notes

Simplified support for external log management systems

Simplified support for external log management systems such as ELK (Elasticsearch, Logstash, Kibana) makes it easier to implement an external log management system. An external log management system can improve access to system log files that help diagnose and debug issues by eliminating the need to download log files from each node in the cluster.

For information about configuring ELK, see Configuring ELK for log management.

For information about using Kibana to view log files, see Pega logs in Kibana.

Customizable New Application wizard

The redesigned New Application wizard streamlines the process of creating and configuring applications, and introduces customizable application templates. When you create an application from an application template, the template defines the wizard steps that gather the information that is needed to configure your new application based on the template. After you specify the required information in the wizard, the system creates an application with the required case types, data types, access groups, and operators. You can create multiple templates, depending on the needs of your business. Sample template types are provided.

For more information, see New Application wizard.

Default quiesce strategy changed to immediate drain

The default quiesce strategy has been changed to immediate drain, which allows you to continue to access a quiescing node to perform actions until the node is removed from the load balancer, regardless of your user role. When immediate drain is enabled, and a node is in the quiesce state, the requestor state is saved after every interaction. After the node has been removed from the load balancer, the saved state can be used to restore the requestor state on a new node in the next interaction with the server.

You can change the quiesce strategy default to slow drain by modifying the value of the session/ha/quiesce/strategy setting in the prconfig.xml file to be slowDrain.

Data APIs support data exploration in React UI tables

Data APIs have been enhanced to support filtering, sorting, paging, and aggregation in React UI tables. You can use that functionality to access your data quickly and intuitively. For example, by using paging, you can query a data page to retrieve the second page of an employee contact list and specify the number of results that are displayed on the page.

For more information, see Data API performance and limitations.

Enhancements to token lifetime limits

Pega Platform™ uses OAuth 2.0 authorization codes, access tokens, and refresh tokens to provide flexible token-based security for applications. Expiration settings for these codes and tokens now adhere to certain strict value range based on industry leading practices. For example, the lifetime specified for the authorization code must be in the range 1-600 seconds.

These can be configured in the OAuth2 Client registration rule form.

For more information, see OAuth 2.0 Management Services.

Automatic creation of large data pages from Report Definitions

Offline-enabled mobile apps now use Report Definitions to automate filtering logic for controls that are based on large data pages. You no longer have to use custom JavaScript functions (custom populators) to create large data pages.

For more information, see How to use large data pages to store large reference data in offline mobile apps.

Improved view authoring

Case authoring in Cosmos React UI now features updated view authoring tools. The redesigned view tab and overlay provide a more intuitive interface for creating views, applying design templates, and adding fields and controls. This enhanced work environment improves the user experience and reduces context switching, which contributes to a lower development effort.

For more information, see Editing views in a case type.

Rule creation and simulations of changes in a change request in the Decision Manager portal

Two major enhancements to revision management give Decision Manager portal users more control over change requests. Revision managers and strategy designers can now create rule instances as part of a regular change request. They also can run data flows to do simulations of changes that are introduced by the change request.

For more information, see Rule creation and simulations of changes in a change request in the Decision Manager portal.

Data transform support in offline-enabled applications

You can now use data transforms in offline-enabled applications to reduce the need to write your own custom JavaScript functions. Data transforms are automatically packaged for offline use when they are configured on flow connectors, as preprocessing or postprocessing data transforms on a flow action, or on refresh actions or data transform actions on controls in a section. You also can run a data transform in offline mode by using a Run Script action or a custom JavaScript function, provided you add the data transform definition to the rule of offline-supported data transforms.

For more information, see Data transform support in offline mode.

Language detection option in Text Analyzer

On the Text Analyzer form, you can identify the language of incoming records based on their language metadata tag by selecting the Language detected by publisher option. This option applies only to Text Analyzer rules that process Twitter records. By combining this option with the advanced language filtering criteria of Twitter data sets, you can filter out unnecessary data and analyze only the Twitter records that are relevant to your business objective.

For more information, see Configuring advanced filter conditions for Twitter data and Configuring language settings.