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.

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.

Decision Strategy Manager

Valid from Pega Version 7.1.3

Fixes were made that improve the configuration and execution of Batch Decisions. In particular,  the capability to use Structured Data has been enhanced. Some notable improvements have also been made to the UI of Visual Business Director.

  • The structured data input configuration will now work even though there is no data.
  • VBD has been enhanced to work with Version 7.1.
  • The structured data input configuration will now work with nested structures.
  • Association rules from Version 6.3 will now work with 7.1 structured data.

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.

User Interface

Valid from Pega Version 7.1.3

Issues for cross-browser support for Designer Studio have been addressed. Improvements were made in run-time performance for data pages with grids, and a number of cosmetic changes and fixes were made.

  • Improved loading of Javascript files during saving Harness rules.
  • Login Performance improvements
  • A cursor pointer issue was addressed in Case Manager.
  • In reports, data in columns will now right-align.
  • Improved section validation functionality
  • Harnesses with screen layouts will now save when there is a refresh condition on a panel.
  • Outline View tree has been improved.
  • Improvements to Repeat Grids using Data Pages as a source.
  • Formatted text cells can be put into a grid to display the value of a property retrieved from a Report Definition join.
  • Designer Studio changes to support IE9 and IE10.
  • Improved designer studio layout
  • Designer Studio changes to support quirks mode in IE8 and IE9.
  • Improvements to SmartLabels in Data Pages
  • Tab groups will take parameters for pre-activities in a defer load setup.
  • Sections support nested dynamic layouts.

Use JDBC 4 compliant drivers for better performance

Valid from Pega Version 7.1.7

For better performance, ensure that you are using JDBC 4-compliant drivers.  For more information on supported and non-supported JDBC drivers, please reference the Platform Support Guide.

Use Tomcat 7 for better performance

Valid from Pega Version 7.1.7

For better performance with a Tomcat web server, use Tomcat 7.

Tomcat 6 has a limitation that causes the server to treat the JDBC driver as if it were a JDBC 3-compliant driver, even if the system is using a JDBC 4-compliant driver. Customers using Tomcat will see better performance if they upgrade to Tomcat 7 and use a JDBC 4-compliant driver.

Engine will not start if the incorrect JDBC driver is used

Valid from Pega Version 7.1.7

The engine will not start up if the incorrect JDBC driver is used. The following configurations are unsupported:

  • Using a Multi-tenant Oracle system with one of the Oracle JDBC drivers with issues (see the chart in the Platform Support Guide)
  • Using a Multi-tenant system with a JDBC 3 compliant driver, OR with Tomcat 6 (for more information on using tomcat with Pega 7.1.7, see Use Tomcat 7 for best performance)
  • Using Microsoft SQL Server with a JDBC 3 compliant driver, OR with Tomcat 6 (for more information on using tomcat with Pega 7.1.7, see Use Tomcat 7 for best performance)

When any of these unsupported configurations are encountered, Pega 7 will not start. Before this change, the engine would appear to start up properly, but would encounter issues during other parts of the engine startup or during actual use of the system.

Noticeable differences between work objects created in the Decision Manager portal when compared to Designer Studio

Valid from Pega Version 7.1.7

In the Decision Manager portal, you create work objects by running flows in the enterprise application that serves as the base application for the application overlay. If the enterprise application does not include the UI-Kit-7 in its application rulesets, work objects can display differently in the Decision Manager portal when compared to Designer Studio because an application overlay is always configured to include the UI-Kit-7 ruleset.

Recommendation:

  1. Add the UI-Kit-7 ruleset dependency to the enterprise application.
  2. Redesign the user interface to comply with the UI-Kit-7 ruleset.

IBM WebSphere Application Server V8: Edit the URL for Enabling System Management Application

Valid from Pega Version 7.1.7

WebSphere 8 does not correctly resolve the URL to enable System Management Application. As a workaround, when you configure the application server, you can do either of these actions:

  • Enter the full URL in the format:
    ​http://hostname:port/prsysmgmt/getnodes.action

  • Set the com.ibm.ws.webcontainer.redirectcontextroot property to true.

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