Published Release Notes

View the configuration settings for Pega Platform nodes in Designer Studio

On the new Configuration Settings landing page, you can view a list of the configuration settings for a specific node, current or remote, or for an entire cluster. From this landing page you can diagnose settings issues, determine whether settings are loaded correctly, and review the settings' purposes. You can also download the prconfig.xml file for any node in a cluster to modify the settings. The ability to view settings for all nodes in the Cluster from a single landing page makes diagnosing configuration issues across the cluster simpler and easier than logging on to each node individually to view its system settings. For example, if a started agent does not run, you can check if agents are enabled on your system; or if some of your caches are too big, you can check the setting for the cache size. You can also determine if settings are loaded correctly, and identify discrepancies in the settings across the nodes.

For more information, see Viewing the current configuration settings of a node or the whole cluster, Downloading and viewing the prconfig.xml file for a specific node, REST APIs for viewing the configuration settings for Pega Platform.

Saving data without using an activity

You can now define data pages to persist data to a system of record. Savable data pages provide a simple way to save data pages without needing to configure an activity. List savable data pages on a flow action to provide users with the ability to update values and save the changes with a savable data page. Use a Save Data Page smart shape to save data as a part of case processing.

For more information, see Creating a data page to save data.

Improved connection pooling performance

HikariCP is now used for connection pooling for databases that are configured by using a URL. HikariCP improves connection pooling performance; however, more database connections might be used than in previous versions of Pega^® Platform.

As a result of the switch to HikariCP, you cannot use the System Management Application (SMA) to get diagnostic data from your application. For instructions about how to get diagnostic data by using REST services, see Obtaining connection pool diagnostic data by using REST services.

Navigation support for test ID

The Navigation rule supports the addition of a test ID to each node. Test IDs support automated testing by providing a unique identifier for user interface elements. Add Test IDs to a navigation rule in the rule form configuration.

For more information, see Navigation form - Completing the Editor tab.

New PEGA0097 alert

In Pega Cloud, if a user attempts to establish a session and the configured maximum number of HTTP requestors on the cluster has been reached, the user is directed to a page that displays the PEGA0097 alert message. This alert helps to prevent a system from becoming overloaded.

For more information, see PEGA0097 alert.

Stakeholder management extended to case followers

You can now control which users follow a case. By actively involving the people with relevant skills and roles in your application, you can resolve cases more quickly.

For more information, see Case followers.

Support for templated auto responses during email triaging of interaction cases

When you triage an interaction case by email, you can now select a predefined email response to provide feedback to a customer more quickly. The category that is associated with this email determines the type of responses that you can select. You can create an email response template or use an existing template.

For more information, see Defining suggested replies for the Email channel.

Configure role dependencies to grant access rights

You can configure role dependencies in a role to grant access rights, which are inherited from the role. Role dependencies are relationships between roles that mirror an organization hierarchy or a more complex relationship among groups of operators, roles, or functional areas. Use role dependencies to simplify role configuration, minimize the number of roles needed by an access group, and minimize the number of privileges that you have to manually define for roles in your application.

For more information, see Access Role rules, Access Role form – Using the Role tab.

Pega Platform ends support for Java 7

Oracle has ended support for Java 7 and is no longer issuing security patches for Java 7. Therefore, starting with Pega 7.4, Pega® Platform no longer supports Java 7. For more information about supported platforms, see the Platform Support Guide. For more information about Oracle support for Java 7, see the Oracle documentation.

Improved operator security

To improve security, Pega® Platform now requires the following:

• During deployment, you must configure a password for [email protected].
• The administrator must enable new out-of-the-box operators.
• The administrator and new Pega-supplied operators must change their passwords after the first login.

These requirements replace the optional secured mode in earlier versions of Pega Platform.