Published Release Notes

Record Editor and data import enhancements

The Record Editor and Import wizard for data types have been enhanced to make the import process faster and easier to use. You can now perform the following tasks.

• Configure the Record Editor to use full-text search, which makes searching faster.
• Configure the location of the data import error file. For example, you can set the location to a shared location so that users can access the file from any node in a multinode system.
• Pass the keys of the records that were added, updated, or matched directly to custom postprocessing without additional database I/O.
• Search and filter records and export only the results instead of all records.
• Stop an import that is in progress.

Full support for Unicode characters in Pega Express

Pega^® Express now supports Unicode characters when you name properties, case types, and data types. Languages that use multibyte characters, such as Japanese and Hindi, are now fully supported. An administrator can enable Unicode support for Pega Express by configuring a Dynamic System Setting in Designer Studio.

For more information, see Enabling Unicode character support for object names.

Enhanced functionality of the Decision Manager portal

The Decision Manager portal now provides more revision management options. The Decision Analytics work area for development of predictive, adaptive, and text analytics models is now part of the Decision Manager portal. PegaUnit testing of rules is more convenient from a new Automated Testing landing page. Revision managers can reassign change requests back to strategy designers or other users of the Decision Manager portal without losing changes that were already made.

For more information, see Enhancements to the Decision Manager portal.

Listener management in Designer Studio

On the new Listener Management landing page, you can view and manage available listeners across the cluster, including on the current node and remote nodes. By using this landing page, you can quickly debug and trace listeners. You can start, stop, and restart listeners, and you can filter the list of listeners by, for example, type, status, class, or name.

For more information, see Managing listeners.

Enhancements to PegaUnit test cases

Several enhancements have been made to PegaUnit test cases.

• You can now use the following new comparators for the page assertion:
  • Has errors – The assertion passes if the system finds all the pages for which there are errors.
  • Has no errors – The assertion passes if the system finds all the pages for which there are no errors.
• You can now export a list of all the PegaUnit test cases that are in the system or that are configured on a specific rule type to Microsoft Excel format.
• You can now view PegaUnit test cases for built-on applications.

For more information, see the Configuring page assertions and Exporting PegaUnit test cases help topics.

Create email correspondence by using templates

You can configure email correspondence rules by using email templates. Email templates provide custom email formats for users and give developers a greater degree of customization in designing email correspondence. Select an email template on the Corr tab of a correspondence rule by clicking Edit mode and selecting Templated email from the menu. You can also create a section as an email template by clicking Email template on the Settings tab of the section form. For more information see Creating email correspondence by using a template.

OAuth 2 token support in Pega Mobile Client

The Client Store module in Pega Mobile Client has been extended to support OAuth 2 tokens. The tokens are used to authorize data synchronization requests that are sent to the Pega^® Platform. Once the OAuth 2 token support is turned on and configured on the server, Pega Mobile Client starts using it automatically. This functionality is available on both iOS and Android devices.

For more information, see Enabling data synchronization with OAuth 2 tokens.

New Java API improves JSON serialization

By using a Java API, you can serialize a Page or Property clipboard object to a JSON string for faster JSON serialization. You can also create a map between API responses and an application's internal data model that improves integration performance and maintainability.

For more information, see Using the mapping API for high-performance JSON serialization and Using the mapping API for high-performance JSON deserialization.

External keystore support in Pega Platform

Pega^® Platform now provides the ability to source certificates and encryption keys from external keystores. You use the Keystore rule to specify alternatives to the platform's database to source certificates and keys. You can choose to use a data page, a URL, or an external file in one of the following standard formats: JKS, JWK, PKCS12, KEYTAB, or KEY. Keystore information is stored in cache memory only. It is not stored on the clipboard nor is it directly accessible to the application logic.

For more information, see Creating a Keystore data instance.

Two-factor authentication with one-time passwords

Pega® Platform now supports two-factor authentication in custom authentication services and case flow processing, by sending a one-time password to an operator through email and requiring the operator to provide it back to your application for verification. Use REST API OTP Generation to generate and store one-time passwords, and REST API OTP Verification to verify passwords against user entries. You can also use the pxSendOTP and pxVerifyOTP activities called by these APIs to implement two-factor authentication of users in case flows prior to performing a critical operation (e.g. before completing a critical transaction such as a funds transfer in excess of a certain amount). Settings on the Security Policies landing page control the behavior of the two-factor authentication process.

For more information, see Enabling security policies.