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-117114 · Issue 171740

Added localization formatting for date values (YYYY-MM-DD)

Resolved in Pega Version 7.1.7

In Sweden, dates are given with a hyphen "-" and not slash "/" as the date separator as per ISO-8601. The SV localization has been changed to follow this style.

SR-117855 · Issue 171394

Resolved NPEs during case creation

Resolved in Pega Version 7.1.7

If a null pointer error was generated during the case creation process, all subsequent records being processed also generated the error. This issue occurred when adding and later removing work party data, and was found to be related to a stack trace not being generated for the reported issue and an attempt to index a change to a page that's no longer available. To correct this, a code change now handles the condition which caused the NPE (writes an index for a non-existent page and then skips it) then logs information for analysis.

SR-117928 · Issue 174886

Improved error handling for 'Response Data Transform'

Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7

When creating a data page with 'List' structure and 'Connector' as datasource, it is mandatory to use 'Response Data transform' (Else throws an error and unable to save data page). However, when 'Response Data Transform' is used, connector error handling details (pyStatusValue, pyHTTPResponseCode and pyStatusMessage) are not saved to the datapage. To correct this, the system has been updated to always call 'response data transform' even in failure cases, enabling the mapping of the error information coming from the data source page (intermediary page) onto the primary data page.

SR-117428 · Issue 169351

Resolved performance issues when R-D-E referenced a data page

Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7

If a declare expression referenced a data page, loading or refreshing a section in update mode caused Rule-Declare-Expression to check whether inputs had changed. The R-D-E then loaded the data page (but didn't pass any parameters), causing the data page to load the max number of pages allowed. Subequently, a series of other R-D-Es fired on that data page as inputs had changed, ending up with a large number of R-D-E's firing that weren't required for a section. As a result, the elapsed time was higher than expected for every screen where this was happening and CPU consumption was high. Auto Population should only trigger on reference to a non-key and non-param property, and this has been implemented.

SR-117428 · Issue 170976

Resolved performance issues when R-D-E referenced a data page

Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7

If a declare expression referenced a data page, loading or refreshing a section in update mode caused Rule-Declare-Expression to check whether inputs had changed. The R-D-E then loaded the data page (but didn't pass any parameters), causing the data page to load the max number of pages allowed. Subequently, a series of other R-D-Es fired on that data page as inputs had changed, ending up with a large number of R-D-E's firing that weren't required for a section. As a result, the elapsed time was higher than expected for every screen where this was happening and CPU consumption was high. Auto Population should only trigger on reference to a non-key and non-param property, and this has been implemented.

SR-118567 · Issue 167257

Enhanced task queue handling for custom applications

Resolved in Pega Version 7.1.7

In some situations, a custom agent would periodically fall over when processing a large backlog of queued items. This was caused by an exception thrown when placing a task in the queue when it is already present. The system has been updated to better handle this situation and allow agents to continue to execute with the present schedule when a duplicate task is found.

SR-117958 · Issue 166117

Alignment issues with IAC resolved

Resolved in Pega Version 7.1.7

When a dynamic layout of stacked style was used in conjunction with IAC, resizing the window caused the elements to not be properly aligned. CSS issues in the HTML handling of overflow properties have been corrected with the resizing harnesses.

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