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-C93344 · Issue 431349

Bcrypt password hash increased to 2^12

Resolved in Pega Version 8.1.4

Bcrypt password hashes have been increased to 2^12 iterations for new passwords.

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.

SR-D45101 · Issue 512530

Added support for Helper Text Question Mark with visibility condition

Resolved in Pega Version 8.1.7

The Helper Text Question Mark was not displaying if the control was configured with "Help icon with overlay on hover" combined with a visibility condition. This was a missed use case, and the expression visibility support for controls.changes have now been added in the pzpega_ui_DLCellTemplate.js file.

SR-D5904 · Issue 490489

Discard changes dialog now showing for local actions

Resolved in Pega Version 8.1.7

After having modified case data without saving and clicking on a menu entry (left menu, search, ...), the system shows a dialog box to ask the user to confirm it is ok to discard changes. However, this confirmation dialog did not work with local actions, leading users to lose their work without any warning nor any way to step back. This was traced to a difference in the dirty form check, which was not present when launching a local action from a case. An enhancement has now been added to the handleMenuAction js function in pypega_ui_harnessactions.js which will perform a dirty form check with a prompt.

SR-D23723 · Issue 503090

pxGenerateExcelFile updated for handling blank dates

Resolved in Pega Version 8.1.7

When using a custom template for exporting to Excel, blank DateTime property column values defaulted to the current date. To resolve this, the pxGenerateExcelFile activity has been updated to ensure that an empty date will be exported as blank and that given dates will appear in the correct datetime format.

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