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-129928 · Issue 198643

Corrected naming difference for DateTime validation

Resolved in Pega Version 7.1.8

If the short description of a date or dateTime type property was different from the property ID, at runtime the required DateTime fields did not turn red when validation failed. This was caused by the Input ID for the datetime field being generated with the property short description instead of the property name. This has been fixed.

SR-129955 · Issue 199160

Extraneous 'save changes' popup removed from PDF viewer

Resolved in Pega Version 7.1.8

A popup asking "Do you want to save changes to pdf before closing" was appearing when closing an unmodified PDF generated from PRPC using the concatenateEforms feature. This was caused by an unneeded appearance setting, which has been removed.

SR-129959 · Issue 198657

Corrected deferred load being called twice in collapsible dynamic layouts

Resolved in Pega Version 7.1.8

In some cases, a collapsible dynamic layout with a deferred load activity would have that deferred load called twice during runtime. This has been resolved.

SR-129970 · Issue 196736

Clicking Radio button label will execute control action

Resolved in Pega Version 7.1.8

When a Radio Button with an action is embedded in the cell of a Repeating Grid, clicking the Radio Button selected the value and executed the Control Action but clicking the Radio Button Label did not. This has been corrected with an added eventString on for actions on child elements in pzGenerateRadioGroup.

SR-129988 · Issue 197489

Updated API for postvalue checkbox handling

Resolved in Pega Version 7.1.8

In a Repeating Grid, the select all check box with PostValue action in the header was showing an HTML response message on reselect after deselecting all the individual checkboxes, and the master checkbox disappeared. This was caused by the wrong context page being sent and the API has been updated to fix this.

SR-130029 · Issue 197162

Localization added to filter control grid in Listviews

Resolved in Pega Version 7.1.8

Localization has been added to the popup opened on click of "Click to filter by" in Listviews.

SR-130067 · Issue 197823

Updated API for opening WB assignments on certain iPads

Resolved in Pega Version 7.1.8

On IOS 7.0.3 4th Gen iPads, attempting to open any workbasket assignments generated an "Empty Assignment Key" error. This was caused by the querySelectorAll browser API not returning correct results in this scenario, and has been corrected by modifying the evaluation method to use the document.evaluate method API.

SR-130101 · Issue 196914

Update to add portal compatibility for Microsoft Internet Explorer 11

Resolved in Pega Version 7.1.8

A meta tag has been added to the frameset HTML rule to ensure compatibility with the Microsoft Internet Explorer 11 browser to access the User and Manager portals.

SR-127173 · Issue 192701

Resolved save error for custom date format

Resolved in Pega Version 7.1.8

A custom date entry given Display mode 'Text Input + Calendar' and the option 'Display value using read-only formatting' and using the format dd.MM.yyyy returned the error 'Entered date value is Invalid' when attempting to save. This was an issue where the processOnBeforeSubmit function code exists to replace the client formatted value with the value which need to be submitted but doSave was using the submitWhenFail API where it has its own logic to process elements. To resolve the issue, the system will call a common function from both places to obtain the proper setting.

SR-127452 · Issue 192406

Case match duplicate check resolved

Resolved in Pega Version 7.1.8

A case match rule to check for duplicates with adding an expression in weighted condition was giving a runtime error due to incorrect page referencing in java step of activity 'RunDuplicateCasesReport' that was attempting to obtain the property from the RD page (which was using a different structure). The page reference has been updated to correct this issue.

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