Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-128987 · Issue 195605

Dynamic Layouts incorrectly shown as not accessible

Resolved in Pega Version 7.1.8

Dynamic Layouts were incorrectly shown as not accessible in the Accessibility Report. This has been corrected. However, please note that the report's requirement to run in Quirks mode to render properly and be functional made it incompatible with modern browsers, and the Accessibility Report has been deprecated and removed. Developers are encouraged to use third party tools such as FireEyes to assess their application from an accessibility compliance perspective.

SR-118106 · Issue 174462

Improved accessibility for UI properties

Resolved in Pega Version 7.1.7

When a property is put on the UI from a different Page the generated UI was not setting the correct LabelFor - it striped the Page context but didn't strip the dot from the front of the property. Accessibility JAWS and other assistive technologies were therefore not associating the label with the input and did not read it out for the given input. The label generation function has been changed to address the reported issue.

SR-A3697 · Issue 210718

Resolved Revalidate and Save freeze

Resolved in Pega Version 7.1.9

After upgrade, running revalidate and save on imported rules with the option "During Update Move To?" enabled, the first rule was processed but the process then stopped and generated the error "Uncaught TypeError: parentRow.all is not a function" if the Google Chrome or Mozilla browser is used. This problem was caused by old non-auto-generated controls, and has been resolved by modifying the ShowBulkUpdateList html section.

SR-A11817 · Issue 233321

Skim_Validate rule made available

Resolved in Pega Version 7.2.1

In order to resolve issues with Offer flow rules not being moved after skimming the ruleset, a new version of Skim_Validate was added to Rule-Obj-Flow-Offer, deleting all steps except for the call to Rule-.Skim_Validate. To make this function fully available, Skim_Validate has now been marked as available to allow extending the activity to a rule form.

SR-A14914 · Issue 231019

Onclick works with single quotes in button label

Resolved in Pega Version 7.2.1

A single quote in the label of a button was breaking the onclick functionality. This was a particular issue when using the French locale, as the localized value for "End other session to Release Lock" is set to "L'autre extrémité session pour déverrouiller".  This has been fixed by removing pega:lookup tag RUF GenerateButton and adding a call to get the localized value and escape that value.

SR-A23970 · Issue 249825

RecreateIndexesForClass OOM resolved

Resolved in Pega Version 7.2.2

Running the activity RecreateIndexesForClass after creating a new Declare index rule in order to reindex old existing work objects was causing a JVM OOM error that required a restart. This was traced to the API fetching all of the records at once to reindex and save, and has been resolved by modifying the function to do an Obj-browse of all the instances and reindex/save the instance one by one.

SR-A94083 · Issue 266677

SaveCovered checks for stale Cover

Resolved in Pega Version 7.2.2

When resolving a Covered work object, a stale copy of the Cover was being saved which resulted in the opened Cover assignment becoming invalid. This was caused by the SaveCovered function not checking to see if pyWorkCover was stale or not before calling RecalculateAndSave. This has been resolved by adding steps in SaveCovered to check if pyWorkCover is stale and to open pyWorkCover if it is stale using Obj-Open-By-Handle.

SR-A97281 · Issue 263948

SaveCovered checks for stale Cover

Resolved in Pega Version 7.2.2

When resolving a Covered work object, a stale copy of the Cover was being saved which resulted in the opened Cover assignment becoming invalid. This was caused by the SaveCovered function not checking to see if pyWorkCover was stale or not before calling RecalculateAndSave. This has been resolved by adding steps in SaveCovered to check if pyWorkCover is stale and to open pyWorkCover if it is stale using Obj-Open-By-Handle.

SR-A99477 · Issue 266058

SaveCovered checks for stale Cover

Resolved in Pega Version 7.2.2

When resolving a Covered work object, a stale copy of the Cover was being saved which resulted in the opened Cover assignment becoming invalid. This was caused by the SaveCovered function not checking to see if pyWorkCover was stale or not before calling RecalculateAndSave. This has been resolved by adding steps in SaveCovered to check if pyWorkCover is stale and to open pyWorkCover if it is stale using Obj-Open-By-Handle.

SR-B426 · Issue 271503

Error label highlighting corrected for inside grid

Resolved in Pega Version 7.2.2

The correct label associated with the UI element in which the client side error was thrown was not highlighted when inside a grid. To fix this, the function findLabelFor has been updated to handle the case specific to the grid, as the error elements ID and the label's 'for' attribute were never equal due to the 'for' attribute changing value when used on repeating elements within a grid.

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