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-D80223 · Issue 542923

Cross-site scripting filtering for ActionStringID

Resolved in Pega Version 8.5

Cross-site scripting filter logic has been added to the ActionStringID function.

SR-D73510 · Issue 538664

Cross-site scripting filtering for ActionStringID

Resolved in Pega Version 8.5

Cross-site scripting filter logic has been added to the ActionStringID function.

INC-142118 · Issue 597313

Data Migration Import/Export made more resilient

Resolved in Pega Version 8.6

The entire data migration operation (export or import) was marked as "FAILED" even if the operation failed for just one type of data. While managing the failure, the operation deleted any completed data flow runs as part of the clean-up and only retained the failed data flow runs for use in further analysis. Because the queued runs could not be deleted, the data migration case became a broken process. At the root of the issue, the data export work item was failing due to one or more DSM service nodes being non-functional based on a validation failure in the case type that runs a check for the presence of functional DSM nodes before starting the data migration operation. This validation can return false negatives, especially on Cloud where the nodes are usually swapped seamlessly without the function realizing it. In such cases, the validation function returned false despite the DSM service nodes being up and running. This has been resolved by adding handling for the failed data migration case by stopping and deleting the open data flows and by disabling the validation which checks for functional nodes.

SR-D6769 · Issue 469284

Corrected tab closing issue for multiple clicks of Get Next Work

Resolved in Pega Version 8.3

While clicking multiple times very fast on a link configured with Get Next Work action, multiple tabs were getting opened with the same work object details and were not auto closing. This was traced to Issue with a stale conflictingHost in the handleGadgetLoad function, and updates have been made to the handleGadgetLoad function so it will get a new conflictingHost if the action is getNextWorkItem.

SR-D6769 · Issue 469285

Corrected tab closing issue for multiple clicks of Get Next Work

Resolved in Pega Version 8.1.6

While clicking multiple times very fast on a link configured with Get Next Work action, multiple tabs were getting opened with the same work object details and were not auto closing. This was traced to Issue with a stale conflictingHost in the handleGadgetLoad function, and updates have been made to the handleGadgetLoad function so it will get a new conflictingHost if the action is getNextWorkItem.

SR-D6769 · Issue 471240

Corrected tab closing issue for multiple clicks of Get Next Work

Resolved in Pega Version 8.2.2

While clicking multiple times very fast on a link configured with Get Next Work action, multiple tabs were getting opened with the same work object details and were not auto closing. This was traced to Issue with a stale conflictingHost in the handleGadgetLoad function, and updates have been made to the handleGadgetLoad function so it will get a new conflictingHost if the action is getNextWorkItem.

SR-122641 · Issue 182813

Edit filters repaired for Report Definition text fields with Microsoft Internet Explorer 9 & Microsoft Internet Explorer 11

Resolved in Pega Version 7.1.8

Using Microsoft Internet Explorer 9 and Microsoft Internet Explorer 11, all of the Report Definition text Fields (including auto complete) in the Edit Filters were disabled and would not accept input when trying to select the property using the mouse. To resolve this, the UI functions have been modified to handle range text native functions for these browsers.

SR-122641 · Issue 181600

Edit filters repaired for Report Definition text fields with Microsoft Internet Explorer 9 & Microsoft Internet Explorer 11

Resolved in Pega Version 7.1.8

Using Microsoft Internet Explorer 9 and Microsoft Internet Explorer 11, all of the Report Definition text Fields (including auto complete) in the Edit Filters were disabled and would not accept input when trying to select the property using the mouse. To resolve this, the UI functions have been modified to handle range text native functions for these browsers.

SR-129249 · Issue 194654

Accessibility added to pxDataField and VisualizeAttachingScreen

Resolved in Pega Version 7.1.8

Accessibility has been added to the out-of-the-box functions pxDataField and VisualizeAttachingScreen.

SR-A11563 · Issue 224698

XSS security update for TabbedRepeatingListSection

Resolved in Pega Version 7.2

Security updates have been made to the TabbedRepeatingListSection function to close a potential XSS vulnerability.

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