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.

Search and Reporting does not index large items

Valid from Pega Version 8.5

When using the Search and Reporting (SRS) microservice in Pega Platform™ 8.5, you might encounter problems with indexing large out-of-the-box rules. The issue is not visible in Queue Processors, but you can access logs to verify which items the system does not index.

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.

Slow WebSphere performance on Mac platforms

Valid from Pega Version 7.1.2

Use the following JVM setting to improve WebSphere performance on Mac platforms:

-Djava.net.preferIPv4Stack=true

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.

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.

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.

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.

Rule revalidation after updating properties without restarting nodes

Valid from Pega Version 8.2

When you update certain property attributes, such as a property's maximum length, rule types that reference the property might not reflect the change. You do not always have to restart nodes to revalidate the referencing rules when they cannot be resaved, for example, when they are in a locked ruleset. For Pega Platform™ 8.1 and later, for non-stream rules, such as activities, data transforms, and so on, use the reassemble API in Admin Studio or truncate the assembled classes table.

For stream rules, such as sections, harnesses, paragraphs, and so on, reassemble the rules and restart the nodes. For more information, see More about properties.

For previous versions of Pega Platform, use the System Management Application (SMA) to revalidate stream and non-stream rules.

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