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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

INC-141451 · Issue 601141

Radio button helper text is localized

Resolved in Pega Version 8.4.4

The localized value from content was not being served for helper text in a radio button group. This has been resolved by adding the necessary localization support to the button template.

INC-142066 · Issue 600046

Dirty confirmation alert added for standalone Ajax container

Resolved in Pega Version 8.4.4

In the Pega CS interaction portal, an interaction could be launched to create a service in the Ajax container. If the same service was opened from the search results or the worklist, however, it was not prompted with the dirty popup message to save or discard the changes. This was a missed use case for a standalone Ajax Container, and has been resolved by adding a check to evaluate whether the document has an Ajax Container so the proper dirty state handling will be called.

INC-142214 · Issue 601790

Null Checks added for Null Dereference

Resolved in Pega Version 8.4.4

Null checks have been added to CSSAsJson and to the activeValue variable, which is used for the checked attribute generation.

INC-142557 · Issue 600532

Accessibility added to Recents

Resolved in Pega Version 8.4.4

Under all recent items, the work object was not opened when using the keyboard and the focus was on the work object. Clicking with the mouse worked. Investigation showed that on pressing the enter key, actions were not triggered because the action string was not on the same SPAN tag (but in child node). This has been resolved with an update to add tabindex on the same span where action-string is added. In addition, accessibility was not enabled on the out-of-the-box Recents table because the work object elements in the table used a formatted text control; this has been updated to use a link control which will enable the accessibility feature while using keyboard navigation.

INC-142557 · Issue 600529

Accessibility added to Recents

Resolved in Pega Version 8.4.4

Under all recent items, the work object was not opened when using the keyboard and the focus was on the work object. Clicking with the mouse worked. Investigation showed that on pressing the enter key, actions were not triggered because the action string was not on the same SPAN tag (but in child node). This has been resolved with an update to add tabindex on the same span where action-string is added. In addition, accessibility was not enabled on the out-of-the-box Recents table because the work object elements in the table used a formatted text control; this has been updated to use a link control which will enable the accessibility feature while using keyboard navigation.

INC-142564 · Issue 598698

Resolved issue with opening case in review mode

Resolved in Pega Version 8.4.4

After upgrade, using the Open in Review button from the Dashboard to view a case that the user did not have work entitlements on opened the case as expected, but the screen then immediately refreshed and redirected to the home screen. This was traced to the button configuration having an incorrect action set, with cancel action and then OpenWorkByHandle, and h as been resolved by updating the open in review button to remove the cancel action.

INC-143310 · Issue 601206

Added scrolling for fixed size modal with buttons offscreen

Resolved in Pega Version 8.4.4

After upgrade, the modal format "Large Fixed" for the Modal Dialog in a local action was not working as expected when the screen was reduced in size. It as not possible to scroll down the modal dialog, and the "cancel" and "submit" buttons were no longer available. In standard modal, the cancel and submit buttons are always shown in the view port. When the modal is fixed format, the width and height of the modal are set to a fixed size. In that case, if the window is resized it is not possible to navigate to cancel and submit buttons that are offscreen. To resolve this, scroll has been added to allow accessing the cancel and submit buttons in case of fixed size modal that does not fit the window.

INC-143363 · Issue 604365

Added handling for maintaining on-change event descriptor

Resolved in Pega Version 8.4.4

The multiselect control was not reliably posting the values to the configured page list property if the change actions were performed very quickly. Multiselect calls triggerCustomEvents, which handles the schedule for an event: when change actions are entered in a paced way they are not added to a queue, but when performing on-change very fast events are added to a queue and processed later. In this case, the queuing caused the correct event descriptor to be lost because the original event flows were not followed. This has been resolved by adding custom handling which will maintain the event descriptor.

INC-143531 · Issue 598645

Dirty Flag reset updated

Resolved in Pega Version 8.4.4

After opening a case in Cosmos, making updates, and then navigating away without saving, the dirty flag message appeared as expected and offered the option to save, discard, or cancel. After clicking on save and opening the next case, performing the same steps did not cause the dirty flag to display when navigating away. This has been resolved by updating the reset of the isDirtyDialogOpen inside the hide API of a modal close.

INC-143599 · Issue 598772

Non-template RDL time value handling updated

Resolved in Pega Version 8.4.4

The Time value displayed on clipboard and data designer differed from the value shown on user work form when using a categorized repeating dynamic layer rendered in non-template mode with the Datetime control configured inside the RDL. This was traced to the Time string being considered as a date when using this configuration and calling the engine API, and has been resolved by ensuring this configuration will call the correct Time API instead so that the timeofday property value will be formatted correctly.

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