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.

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.
  • 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.

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. 

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.

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.

Integration

Valid from Pega Version 7.1.4

Critical customer-driven product improvements were made to SOAP services, SOAP connectors and connector wizard, CMIS connectors, and the Pega Image Viewer. These fixes addressed a handful of functionality gaps discovered in PRPC 7.1 and earlier releases by internal and external customers.

  • A Connect-CMIS instance which was created using a reference to an ATOM Server Instance may now use Global Resource Settings.
  • The Execute Synchronously (one-way operation) has been enhanced for SOAP Services.
  • The Silverlight version of PegaImageViewer has been enhanced to print ranges of multiple pages at once.
  • The SOAP Wizard has been improved to show all the ports which are available in the WSDL file.
  • Two way SSL has been enhanced for the Connect-REST rule.

 

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.

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.

Data Management

Valid from Pega Version 7.1.3

Improvements to data handling were made for the Data Pages, autopopulate properties, and reference properties.  Lightweight lists were optimized.

  • Property references are now maintained on the Work Page.
  • PageList properties can reference a Data Page.
  • Auto-populate properties can be used in a seciton to show results from a Data Page.
  • Data Pages can run in “Page” mode as well as “List” mode
  • The "Rules Not Using Lightweight List" report was enhanced.
  • A PageList property that references a Data Page may be used to populate a grid.
  • Related autopopulated properties can now be referenced.

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