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.

Required Oracle optimization parameter

Valid from Pega Version 7.1.3

To optimize performance, set the Oracle parameter optimizer_index_cost_adj to a value between 20 and 25. If this value is not set, the system can run exceedingly slowly, potentially blocking users from login.

Synchronized database and application server settings

Valid from Pega Version 7.1.3

Configure your database and application server to use the same time zone and character encoding to avoid conflicts.

Case Management

Valid from Pega Version 7.1.3

This release had a focus on extending key capabilities to improve the ease of configuration based on early adopter feedback.  Improvements were made in run-time performance, especially in high volume situations with complex case configurations.  A series of cosmetic changes and fixes are included.

  • The Wait shape now supports dynamic references.
  • Issues were addressed with the CreatePDF and the CascadingApproval Smartshapes.
  • Attachments have been improved.
  • Issues with the Create Case Type functionality were addressed.
  • The Pega Pulse functionality has been improved, including its performance.
  • When auditing a work item, History is now the default tab.

System Management

Valid from Pega Version 7.1.3

The PRPC installer has been enhanced to handle additional error conditions related to partial installs and duplicate keys; additionally, the hotfix rollback feature has been improved, and the Rulebase compare tool now supports HTTP(S) environments.

  • Rollback feature has been enhanced.
  • RuleBase Compare will work for secure (HTTPS) environments as well as  non-secure (HTTP) environments.
  • Install will gracefully handle the presence of a duplicate key during import.
  • When install fails, system will set tables back to original state.
  • Remote MBean methods will now work on multi-servant load-balancing systems.
  • Enhancements were made to harnesses in Split Schema systems.

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.

Set the status of a case on stage entry

Valid from Pega Version 8.1

You can now set the status of a case when it enters a stage. By setting the status of a case on stage entry, you can communicate to stakeholders how close a stage is to resolution. For example, if a case is in the approval stage, you can set the status of the case to "Under review" when the case enters the stage.

For more information, see:

Resolve child cases with the parent case

Valid from Pega Version 8.1

You can now configure a stage to resolve open child cases when the parent case is resolved. Resolving child cases on the resolution of the parent case ensures that no child cases are left open when the parent case reaches the end of its life cycle.

For more information, see:

Conditionally skip a stage

Valid from Pega Version 8.1

You can now define a condition in App Studio and build an expression in Dev Studio that causes a case to skip a stage. The system evaluates the condition or expression at run time and skips the stage if a true value is returned. By skipping the current stage when it is not relevant, you can resolve a case more quickly by moving the case to the next stage in the sequence.

For more information, see:

Conditionally start a process

Valid from Pega Version 8.1

You can now define a condition that causes a case to start a process in a stage. When the condition evaluates to false, the case skips the process. You can resolve cases more quickly by moving a case to the next process in the sequence when the current process is not relevant.

For more information, see:

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