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-230718 · Issue 737341

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-230738 · Issue 741462

Fixed cursor jumping issue for date only input

Resolved in Pega Version 8.8

When selecting a date from the calendar and keeping the cursor in the date part (MM/DD/YYYY) , trying to clear it caused the cursor to immediately jump to the end. This has been corrected.

INC-231076 · Issue 738162

AddMessage function shows error on UI

Resolved in Pega Version 8.8

After updating from Pega 8.1 to 8.6, an addmessage function which previously displayed an edit validate rule error message was not working. This was an issue with textinput inside a grid, and has been resolved by adding a style to input text when it has a symbol left aligned and giving the error icon a z-index to show the message when the symbol is configured.

INC-231145 · Issue 734364

Security improvement for Currency control

Resolved in Pega Version 8.8

A potential cross-site scripting issue related to readonly formatting for the Currency control has been resolved.

INC-231255 · Issue 743958

ToolTip update on repeating dynamic layers pagination options removed

Resolved in Pega Version 8.8

The repeating dynamic layers Tooltip regarding format settings in the property panel has been removed as pagination for user action works for both template and non template.

INC-231316 · Issue 744051

Corrected tab display with collapsed panel

Resolved in Pega Version 8.8

Tabs were not displaying properly in the case view with collapsed summary panel (when there is too many tabs). This has been corrected.

INC-231325 · Issue 738557

Listener timeout added for fetching external content

Resolved in Pega Version 8.8

Email listeners became stuck and did not recover if there was an issue retrieving external content for a message. To resolve this, a timeout setting has been added when fetching external content.

INC-231625 · Issue 735231

Handling updated for fetching chain of archived ancestor cases

Resolved in Pega Version 8.8

Previous work done to show the case hierarchy dropdown for archived cases in the ReviewArchivedCase harness has been further modified to cover additional use cases. The original method to fetch the parent case was "Obj-Open-By-Handle" which supports secondary storage but triggers all declaratives, which may lead to errors under specific configuration. Using "Obj-Browse" instead does not support secondary storage, but does not trigger declaratives. In order to ensure the best coverage for various use cases, this has been updated to conditionally use both methods; the system will use "Obj-Browse" first, and if it fails it will check secondary storage using "Obj-Open-By-Handle".

INC-231711 · Issue 739220

Localized date format based on custom constants

Resolved in Pega Version 8.8

After update, date values were shown with the format itself such as "dd/MM/yyyy h:mm a" instead of the actual date value. This was an unintended side effect of work done to localize the date handling for a specific locale, and has been resolved by updating the setting method to one which uses custom constants available to generate the custom datetime format per locale.

INC-231847 · Issue 737405

DSS added to control validation of hidden fields

Resolved in Pega Version 8.8

When required fields are in hidden format, a client side validation error may be thrown on submit. To address this, a DSS has been added to control whether or not hidden fields are validated. By default "validateHiddenField" will be true and the fields will be validated; changing this to false will skip the validation of hidden fields.

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