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.

CyberArk password vault support added for Pega database

With the CyberArk password vault, you can store your systems' passwords in a secure, central location and retrieve them from that location instead of directly entering credentials into the systems. This support is available only for IBM WebSphere environments.

For more information, see Pega Platform deployment guides.

Support added for multiple mashups

You can now include multiple mashups on a single webpage or browser, even if the mashups have different application and authentication requirements. Use mashups to embed a Pega Platform™ application as a gadget on your website. For example, you can embed Web Chatbot and Self-Service Advisor on the same website.

For more information about mashups, see Configuring the Mashup channel.

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.

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.

Resolve Job Scheduler and Queue Processor rules with the AsyncProcessor requestor type

Use the new AsyncProcessor requestor type to define a default dynamic context to resolve background rules such as Job Scheduler and Queue Processor rules. Switch to an application-based context after you create your own access groups, to resolve only the rules that are included in your application.

For more information, see AsyncProcessor requestor type.

Support for an external Elasticsearch cluster for on-premises deployments

On-premises customers can configure an Elasticsearch cluster that is external to the Pega Platform™ by using client-server mode. Using an external search configuration makes Elasticsearch more highly available and scalable. 

You can view the status of your external Elasticsearch service on the Search landing page. For more information, see link to Viewing the status of an external search service.

REST APIs for system management

New REST APIs are available for reports, agent management, requestor management, cache management, queue processing, and node management. Call these APIs to troubleshoot issues, or perform administrative functions in Cloud applications.

For more information, see Pega API.