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-C93555 · Issue 431600

BulkMover updated to not treat Numerics as strings

Resolved in Pega Version 8.1.4

When attempting to update Pega platform 8.1.1 to 8.1.3 with Oracle on a Windows machine with German locale using the out-of-place upgrade of the rules schema, the migration failed at the migration step with the error message "ORA-01722: Ungültige Zahl". This was traced to BulkMover failing when trying to convert a string to a Numeric due to the locale using commas as the decimal separator, and has been resolved by updating BulkMover to not treat Numerics as strings.

SR-C94950 · Issue 433176

Rule lock is released after alternate approved operator rejects it

Resolved in Pega Version 8.1.4

When using the rule check-in approval process, if a rule check-in candidate was rejected by an approved operator other than the one who checked it in, the lock on the original rule was not released. This has been corrected so the lock is released after the rule is rejected in the case worker portal.

SR-C95232 · Issue 432328

Removed extranous tick mark on negative numbers in Excel export

Resolved in Pega Version 8.1.4

All negative amounts had an extra ( ‘ ) in front when report definition results were exported to Excel. This was a byproduct of a security update, and has been resolved.

SR-C96297 · Issue 433777

Enhancements added in support of AES/PDC integration

Resolved in Pega Version 8.1.4

The following enhancements have been added in support of AES/PDC integration: - QueueStatistics for Oracle and multi-tenant environments -Postgres statistics are reset after every push (this can be disabled by changing the DSS ResetTableStats) -Enabled Debug statements before all connect-rest/connect-soap calls -Handling for Listener Information issues -Elastic search updates -The connect timeout has been enhanced from 30 sec to 60 sec for all REST connectors. -Data pages can be used for picking the End point URL -Elastic Search Count details can be pushed to PDC

SR-C96362 · Issue 433333

XSS filter added to API form handling

Resolved in Pega Version 8.1.4

An XSS scripting filter has been added for properties that can be changed via API.

SR-C96760 · Issue 433394

Resolved system performance issues for clusters of >15 DF nodes

Resolved in Pega Version 8.1.4

The introduction of distributed event logging used to facilitate data flow troubleshooting in Pega 8.1 created a negative impact on performance for extremely large clusters (>15 DF nodes). To resolve this, the distributed logs have been removed and the system will save events in the database instead.

INC-194932 · Issue 686277

Handling updated for offlineWorkIDs map

Resolved in Pega Version 8.8

Intermittent failures were seen when deleting attachments on Mobile. These were traced to pega.ui.DCUtils being undefined, and has been resolved by populating the offlineWorkIDs map for attachment-related actions.

INC-188469 · Issue 714843

Updated retainLock for DoClose activity

Resolved in Pega Version 8.8

After sending an external email notification from a case, attempting to use the "close" button resulted in an access denied error. This was traced to a missed use case for recent security improvements which resulted in not setting the required parameter retainLock for the DoClose activity, and has been resolved.

INC-192673 · Issue 689552

Tab highlighting updated

Resolved in Pega Version 8.8

Not all elements were indicated with yellow highlighting when tabbing through the screen. This has been resolved.

INC-194180 · Issue 704636

GetChildcases handling updated for large numbers of cases

Resolved in Pega Version 8.8

When a very high number of child cases being processed contained a wait shape that was dependent on the movement of a parent case, some of the cases were moved to the next step of the flow automatically while others required a manual command to ResumeFlow. In extreme cases where many child cases were waiting, a node crash could occur. This was traced to the pzGetChildcases report having a maximum value of 500 lines, and has been resolved by increasing the maximum number of rows to retrieve to 9999 in the Data Access Tab of the pzGetChildCases report definition. In addition, the pxCheckFlowDependencies activity has been modified to perform with a higher number of cases, and DSS(MaxRecords) logic has been added to split the child cases into multiple queue items for each access group to decrease load on each thread process.

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