Skip to main content

Published Release Notes

Find release notes for the selected Pega Version and Capability

Browse resolved issues for Platform releases.

This documentation is for non-current versions of Pega Platform. For current release notes, go here.

MBeans deprecated in favor of Pega API

Valid from Pega Version 8.1

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.

Database

Valid from Pega Version 7.1.4

Improvements to data handling were made for search indexing, agent processing, and filtering.  Scripts were provided for proper population of the database tables.

 

  • Importing data from shared obj-external tables is now supported.
  • A validation warning will now display when an unexposed property is used in filter or join conditions.
  • A Global Search index may now be created across two databases.
  • Agent processing on multiple nodes has been improved.
  • Improvements were made to controls in Report Definition pages which are used in a dynamic grid.
  • Filtering functionality involving special characters has been enhanced.
  • Scripts have been provided to populate the RuleSetVersion Major, Minor, and Patch columns.

DCO

Valid from Pega Version 7.1.4

This release focused on improving the user experience of creating new rules and tightening up the use of specifications in the Case Designer.  The layout of the New and Save As forms were made more intuitive and intelligent.  Specification actions were made to be more consistent across various aspects of the Case Designer.

  • After removing specification references, users can create and save a new specification.
  • Developers may now choose either an existing specification or create a new one for subflows and Split-For-Each shapes.
  • If a specification is not associated with flow shapes such as sub flows, Utilities, or Split-For-Each, it is possible to import speciications with the same names, and the flow shapes will default to using those imported specs.
  • In the outline view, specification changes will be preserved when switching from tab to tab.
  • The View Full Details functionality from either Configure Step or the Outline View will display all details, including the specification requirement links.

System Management

Valid from Pega Version 7.1.4

Refinements were made to out-of-place upgrade documentation and processes, as well as for how handling is performed for all of the database vendor specific nuances related to a deploying into a split schema environment.

  • A script was created to run the data schema upgrade for z/OS systems.
  • In a split-schema configuration, indexing has been enhanced.
  • The product installer has been enhanced.
  • The stand-alone Static Assembly Utility does not require a password for its process.
  • The UpdateManager tool has been improved.

REST APIs added for management of agents and requestors

Valid from Pega Version 8.1

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.

Automatically populate columns on import

Valid from Pega Version 8.1

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

Valid from Pega Version 8.1

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

Valid from Pega Version 8.1

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

Valid from Pega Version 8.1

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

Valid from Pega Version 8.1

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.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us