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.

Core Engine

Valid from Pega Version 7.1.4

This release contains fixes related to clipboard and declarative features, including data pages and autopopulate.

 

  • A rule may be changed using Private Checkout, and then checked into a higher RuleSet Version for that RuleSet.
  • Agents may now use a 24-hour time period for scheduling, as well as a 12-hour time period (which required the selection of AM or PM).
  • Caching and performance have been enhanced.
  • Declare expressions will work with embedded page lists when creating forms.
  • Mandatory parameters on a data page can handle blank values.
  • Properties may be auto-populated using a reference property which is created with a Property-Ref method in an activity.
  • System will use "private edit" rules in developer's personal RuleSet when that rule overrides the "standard" rule available to all.
  • The Page-Remove method will now remove Data Pages at the Thread level and the Requestor Level.
  • When copying a page using the "Set" action on a data transform, the Declare Indexes defined on that data will be updated.
  • When creating a data page, the Reload Once per Interaction checkbox can be checked to set the refresh strategy. 

Designer Studio

Valid from Pega Version 7.1.4

Many refinements to the Designer Studio were made around performance and user experience. Based on feedback, we have made a number of bug fixes and strategic improvements that improve the overall user experience.

  • The Developer Portal connects to the PDN's RSS feed without needing a DigiCert certificate for validation. The RSS feed is just headlines; to open and read any of the articles, users will still have to log into the PDN.
  • Expression Builder has been enhanced to work with IE8.
  • New applications built in Version 7.1 will automatically redirect users to the PRPC login page upon logout. A new template has been added, to allow developers to customize their applications to redirect users to a logout page, if they wish.
  • Performance improvements were made when saving and validating rules.
  • Performance of the Guardrails Dashboard has been improved.
  • The display of circumstanced rules in Application Explorer has been enhanced.

User Interface

Valid from Pega Version 7.1.4

This release had a focus around improving support for accessibility for all the PRPC UI Components as well as extending capabilities for responsive design with grids and tabs. A series of cosmetic changes and fixes are included.

  • Improvements have been made for action items being opened in a dynamic container.
  • Row repeat functionality in sections has been improved to better handle source properties.
  • Screen layouts have been optimized for the iPhone platform
  • The display on dynamic containers has been enhanced to provide the same behavior for both single-mode and multi-mode.
  • The Launch Harness feature has been improved to launch into a pop-up window.
  • The operator menu will now display from the Case Manager portal.
  • The Primary Page functionality has been enhanced for control-defined Repeating Tab Headers.
  • Using local actions defined as modal windows has been enhanced to work in an iPAD using a Safari browser.
  • When using a modal dialog to open a flow action in a repeat grid, to add an item to the list, users may now cancel out of this dialog if no changes are needed.

Designer Studio

Valid from Pega Version 7.1.3

Numerous usability improvements were made for this release. A group of cosmetic, functional, and performance enhancements were also included.

  • Treegrid controls work more quickly in IE9 and IE10.
  • On application ruleforms, the 5.4 "Place Properties on Thread Page" checkbox will work in 7.1.
  • Message error handling has been improved.
  • Log messages have been cleaned up.
  • Connectors may now be used in Data Pages.
  • Move Rules wizard has been enhanced to work in Version 7.1.

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.

Automated Unit Testing (AUT) content removed from the help

Valid from Pega Version 7.2.2

Information about Automated Unit Testing (AUT) has been removed from the Pega 7 Platform help, beginning with version 7.2.2. The AUT information is still available in earlier versions of the Pega 7 Platform help and on the PDN in the topic category Testing Applications.

PegaUnit testing is now supported on data pages, activities, data transforms, strategies, decision tables, and decision trees, which you can use to quickly and easily create test cases for your Pega 7 Platform applications instead of using AUT.

For more information, see:

Security fields in JFrog Artifactory repository rule form removed

Valid from Pega Version 8.1

The fields in the Security section of the JFrog Artifactory repository rule form, including the Secure protocol field, the Truststore field, and the Keystore field, were not functional in Pega Platform™ 7.3, 7.3.1, and 7.4. This section has been removed from the JFrog Artifactory repository rule form in Pega Platform 8.1.

Improved UI accessibility

Valid from Pega Version 8.6

Pega Platform™ now supports W3C Web Accessibility Initiative guidelines more fully, which creates a better user experience for people who rely on assistive technologies, such as screen readers.

The user interface now features the following enhancements:

  • Improved keyboard navigation and updated ARIA attributes for layouts, including dynamic, repeating, and table layouts.
  • Updated navigation for AJAX and dynamic containers.
  • More precise keyboard navigation and focus control for pop-up components, such as SmartTips.
  • Fixed accessibility gaps in out-of-the-box actionable controls and form components, such as buttons and text fields.
  • More accessible error messages with improved color schemes and focus control. To meet the WCAG ARIA guidelines, the Show next Error bar has been retired and substituted with more accessible error symbols.
  • Accessibility code included in the Pega Platform ruleset by default, without the need for additional configuration.

For more information, see Supported keyboard navigation.

Improved scroll functionality in vertical tabs

Valid from Pega Version 8.6

When you scroll content in an application that uses the Cosmos theme, the UI now remembers the scroll position even if you switch between vertical tabs, for example, in the case details section. Previously, the application reset the page to the topmost position every time you switched tabs. This update improves the user experience by reducing context switching.

Embedded properties in DX API v2 requests are no longer removed

Valid from Pega Version 8.6

In Pega Platform version 8.5, when you use the POST and PATCH v2 DX API methods with an embedded page property included in the content element of the request, the system removes all properties in the embedded page that are included in the case but are not a part of the request. Now, the merge logic has been modified to update embedded page fields sent up in the request, and keep other fields unchanged.

This feature simplifies client code and prevents data corruption.

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