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-A92162 · Issue 260005

Proposition Filter Strategy logic more flexible for testing

Resolved in Pega Version 7.2.2

The Strategy test run was giving inconsistent results whenever the LOGIC STRING of the Proposition Filter used in that strategy was changed. This was traced to the order of sub-strategy execution, and has been fixed by modifying the component referencing to be execution-order independent and cache the component results regardless of whether the component has been executed or not.

SR-A97134 · Issue 263264

TW connectors made more robust

Resolved in Pega Version 7.2.2

The Twitter data flow extraction has been made more robust with better error handling for any failures the the TW connectors might encounter.

SR-A101936 · Issue 269109

DSM clipboard updated to resolve memory leak

Resolved in Pega Version 7.2.2

There was an issue in DSM Clipboard Page implementation that could cause a memory leak in certain conditions where the clipboard page would unnecessarily keep doubling its inner array (where the properties are stored) every time the replace method was called. The DSM Clipboard Page implementation of the replace method has been modified to not double the inner array when there is no need to do so.

SR-A89158 · Issue 257328

Tuning to speed ADM thread startup

Resolved in Pega Version 7.2.2

Threads were appearing hung during ADM startup due to extended time spent loading model factories from the database into memory. Improvements have been made to reduce this loading time by changing the way in which the models are serialized to / deserialized from the database.

SR-A97899 · Issue 270052

DSM property reference handling updated

Resolved in Pega Version 7.2.2

When a complex property reference was passed to DSM page, it was treated as a simple reference and incorrect results were returned. This has been fixed.

SR-A87923 · Issue 257159

Improved logging for Data Flow exceptions

Resolved in Pega Version 7.2.2

When an error occurred on a source shape in data flow, the page information was not reported in the error report and log. This was due to a handling error that lost the reference of the original page in this scenario, and the system has been updated to improve troubleshooting by retaining the reference and including it in the error report as well as reporting it in regular logs.

SR-A25537 · Issue 256157

Added better handling for campaign records processing timeout

Resolved in Pega Version 7.2.2

When executing a high volume Pega Marketing campaign on a multinode system, the data flow was sometimes dropping input records if the rest of the flow was slow, leading to a stalled run where not all of the records were processed. The handling for this condition has been improved with greater tolerance to ensure all records are processed.

SR-A86679 · Issue 257744

Added better handling for campaign records processing timeout

Resolved in Pega Version 7.2.2

When executing a high volume Pega Marketing campaign on a multinode system, the data flow was sometimes dropping input records if the rest of the flow was slow, leading to a stalled run where not all of the records were processed. The handling for this condition has been improved with greater tolerance to ensure all records are processed.

SR-A88525 · Issue 257026

Added better handling for campaign records processing timeout

Resolved in Pega Version 7.2.2

When executing a high volume Pega Marketing campaign on a multinode system, the data flow was sometimes dropping input records if the rest of the flow was slow, leading to a stalled run where not all of the records were processed. The handling for this condition has been improved with greater tolerance to ensure all records are processed.

SR-A90544 · Issue 258460

Added better handling for campaign records processing timeout

Resolved in Pega Version 7.2.2

When executing a high volume Pega Marketing campaign on a multinode system, the data flow was sometimes dropping input records if the rest of the flow was slow, leading to a stalled run where not all of the records were processed. The handling for this condition has been improved with greater tolerance to ensure all records are processed.

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