Published Release Notes

REST APIs added for management of agents and requestors

You can use new REST APIs to download a module version report or manage requestors and agents in Pega Platform™. For example, you can use a requestor REST API to end a requestor process, and you can use an agent REST API to start or stop an agent. These APIs allow external systems to report and manage Pega resources.

For more information, see Pega API for Pega Platform and Pega API.

Support for multiple custom mobile apps for a Pega Platform application

To enhance the user experience and provide support for native mobile components, you can create multiple custom mobile apps for a Pega Platform™ application. For each custom mobile app, you must create a different mobile channel interface. In addition, you can configure each custom mobile app to run only in a specific portal for an application. The custom mobile app uses this portal regardless of which default portal is defined for the access group.

For more information, see Selecting a portal for a custom mobile app.

MBeans deprecated in favor of Pega API

The use of MBeans for cluster management has been deprecated, although MBeans will continue to function for legacy deployments. The recommended best practice for automating system management is to use the Pega API. For more information, see Pega API.

Apache Ignite is no longer supported

Apache Ignite is no longer supported and has been replaced by Hazelcast Enterprise Edition 3.10 in embedded mode. If you used encryption with Apache Ignite, you can configure encryption on Hazelcast Enterprise Edition in the same way that you configured it for Apache Ignite.

For more information about encrypting nodes, see Enabling encrypted communication between nodes.

Changes in large data page support in offline-enabled custom mobile apps

You can now create offline-enabled custom mobile apps that store reference data in large data pages that are sourced from report definitions, even if these report definitions return no records. Synchronization of these custom mobile apps does not fail. Also, you can now use page type properties as large data page properties.

For more information, see Creating and sourcing large data pages to store large reference data in offline-enabled applications and Custom populator JavaScript functions for large data pages.

Troubleshooting offline-enabled applications in a browser

You can now troubleshoot offline-enabled applications by using the Tracer tool and developer tools that are available in a web browser. You can troubleshoot scripts that are running when the application is running, without having to use additional debugging tools.

For more information, see Application debugging using the Tracer tool, Troubleshooting offline-enabled applications with the Tracer tool in a browser, and Offline capability.

Automatically populate columns on import

If an imported archive file adds columns to existing tables, Pega Platform ™ can automatically expose and populate the new columns during the import. For more information, see Import wizard.

Automatically revalidate and save classes after upgrade

To automatically revalidate and save classes after an upgrade, edit the product rule definition. After you upgrade the application, the classes you specify are revalidated and saved under the application version context you provide. If the application version exists on the target system before the upgrade, the revalidate and save process is not called.

For more information about editing the product rule, see Specifying product rule deployment options.

Add and populate new indexes on import

If you import an archive that includes new indexes, use the Import wizard advanced mode to schedule a post-import job to automatically add and populate the new indexes. For more information, see Import wizard.

Support for native search in custom mobile apps

To improve the overall user experience in a custom mobile app, you can configure native search in the user interface of the application. To use the search capability, first configure the pySearchConfiguration rule. This rule allows you to optionally define a set of search categories as a local data source. You then configure the mobile search action for any user interface control, for example, a button in a section. Users can tap the search field to see the most recent search results, including results that are grouped by categories, as they enter search text.

For more information, see Native search capability in custom mobile apps and Configuring search in custom mobile apps.