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.

INC-228900 · Issue 738197

Archived case history is viewable

Resolved in Pega Version 8.8

Case history was not displayed for archived cases. This has been resolved by adding a section and when condition to display archived case history.

INC-228988 · Issue 742196

Handling added for custom attribute that holds a JSON string

Resolved in Pega Version 8.8

When the DX Assignments API was expected to render a view with a custom attribute that holds a JSON string, it cut the string off at a random point. This caused an error on the front-end screen and the correct view was not displayed. Investigation showed part of the json was incorrectly localized which caused it to treat some values as variables. This has been corrected by testing whether a custom attribute is JSON, and if it is it will be escaped so it is not localized or modified.

INC-229167 · Issue 734199

PD4ML upgraded

Resolved in Pega Version 8.8

Issues with PDF generation have been resolved by upgrading PD4ML to version 4.0.13.

INC-229308 · Issue 739562

ValidateInteger function added to preserve decimal properties

Resolved in Pega Version 8.8

Decimal properties were being automatically changed to integer. This occurred because the edit validate rule on any type of property did not allow decimal entry if the edit validate rule name contained "IsInteger" even if the rule contained no code. To resolve this, the validateInteger function has been added to check whether the validation type is integer.

INC-229714 · Issue 733083

ParentKey handling updated for for CS portal

Resolved in Pega Version 8.8

After creating an interaction in the CPM portal and refreshing the CPMPerformIncludes section (top-level section in the Perform harness) on button click, the focus was set to the first property and a large number of "Uncaught harness context does not exist" error appeared on the console and the screen became frozen. Analysis showed that after the refresh the parentKey property was empty, causing the flow to be executed in the wrong context. This has been resolved by adding a condition to set the parentKey for CS portal 'Add document' scenarios.

INC-229967 · Issue 735962

Number control decimal formatting triggered on tabout

Resolved in Pega Version 8.8

When using the pxNumber control in a section, decimal formatting for input of fewer than 4 digits was not executing unless a post call to the server was triggered. This has been resolved by adding a condition check to format value when there is input of length greater than 0.

INC-230101 · Issue 738063

Menu button no longer steals focus on dismissal

Resolved in Pega Version 8.8

Action menus in the portal harness were stealing focus from input fields in the work harnesses. This was an unintended side effect of work done to correct an issue where focus was not correctly remaining in the table layout, and has been resolved by updating the control menu to avoid the explicit focus in the hideNode function when the menu is already dismissed.

INC-230471 · Issue 733486

Check added for openHandleInNewTab in report flow

Resolved in Pega Version 8.8

The on-click was not working the first time for standard report that was executed via Manager/User portal with the report definition configured to fetch the rowkey as pzInskey. This has been resolved by adding a condition to check whether method openHandleInNewTab exists.

INC-230576 · Issue 741541

Data transform works with encryption in Pega Mashup

Resolved in Pega Version 8.8

Data transform was not getting called in case of Mashup when "Use Encryption" was ON. This was traced to the data transform not being triggered correctly in this scenario, and has been resolved.

INC-230579 · Issue 742038

Inline error message consistent for currency field

Resolved in Pega Version 8.8

After update, an inline validation error triggered on a currency field inside of a text box disappeared when the page was scrolled back to the top. This was traced to the display_removeErrorImage function being called from validation_ValidateFieldOnEvent due to an “onBlur” event, and has been resolved by removing the onblur for a number of decimal type to prevent clearing the validation messages at field level on tab out.

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