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.

INC-133013 · Issue 580951

Corrected white space left after feedback panel collapse

Resolved in Pega Version 8.4.3

After activating the feedback panel on the right side of Cosmos Agile Studio, white space remained in that area after the panel was closed. This was traced to javascript overriding the style of the main panel, and has been resolved.

INC-135405 · Issue 582002

Simple button style updated to allow customization

Resolved in Pega Version 8.4.3

The Simple button style was not picking up the correct border style that was defined in the Skin rule when in the hover state. This was traced to the border radius value hard-coded in one of the custom files taking precedence over the value added for the border radius in the skin format. To resolve this, the simple button styles code has been removed from the controls.css file that had the border radius value hardcoded. The styles for simple button format will be configured in the skin, and a mixin has been added for modal buttons border styles that can be configured in the skin itself.

INC-135554 · Issue 584115

Handling added for displaying very long case ID in Cosmos

Resolved in Pega Version 8.4.3

Case ID and case type were overlapping in the user portal when using Cosmos. This was caused by a case ID that was long enough to cause a line break, and was due to a height being set on the Case ID area. To resolve this, updates have been made which will truncate the display of an over-length Case ID and add ellipses when the text is too long.

INC-136793 · Issue 585602

Updates made to display busy indicator correctly in Google Chrome 84

Resolved in Pega Version 8.4.3

The Pega busy indicator was not displaying correctly in Google Chrome 84 due to changes in that browser. The needed updates have been made to adjust for these changes.

INC-137736 · Issue 585509

Timing issue resolved for modal animation

Resolved in Pega Version 8.4.3

A modal dialog configured with Reveal Animation appeared first without the animation and then disappeared, immediately followed by the animated modal dialog. This was traced to a set timeout that caused the modal to render before the animation, and has been resolved by removing the set timeout.

INC-138886 · Issue 589299

Animated modals correctly trigger refresh conditions

Resolved in Pega Version 8.4.3

In the client application, a list of tasks can be selected by the user to act on. Clicking on any action opens a modal to work on the task. Once that task is complete, the modal is closed automatically, and the task list is updated to show the next task. The task list section has a refresh condition that triggers when D_Reload.pxUpdateDateTime changes (that timestamp is updated when a task is completed inside the modal). However, after upgrade the task list was no longer updating correctly. This was traced to the animation being performed as an asynchronous task: by the time it was executed, the dom element was not present and the refresh section was not getting triggered. This has been resolved.

INC-128406 · Issue 578887

Handling added for radio button with expandpane

Resolved in Pega Version 8.4.3

When given a radio button to select a row in a table (table with Edit Option as Master-Detail - Expand Pane), the first click on the radio button expanded the row but the radio button was not selected. On clicking again, the radio button was selected. The issue was observed in UI gallery as well, and changing the radio button to a checkbox worked as expected. This was traced to a difference in handling related to event infrastructure changes, and has been resolved by adding a timeout in grid specific code for use when there is a radio button with expandpane grid configuration.

INC-128970 · Issue 583292

Post value in grid works after clicking on modal submit

Resolved in Pega Version 8.4.3

The row submit on the grid of the modal dialogue worked when the value was updated and there was a click outside the grid. However, when the value was auto-populated, after clicking on the submit and going back to edit the value in the grid, the row submit did not work. Investigation showed that when a modal was submitted with some server errors, the system replaced the DOM and a new grid is initialized: since some of the listeners related to grid are attached to body, on submit of modal with server errors, these old listeners were getting fired. To resolve this, a safe check has been added for modalDetailsDiv before accessing it in event listeners.

INC-129104 · Issue 578744

Mashup updated to support Safari 13.1

Resolved in Pega Version 8.4.3

Starting with version 13.1, Safari has enabled the “Prevent cross site tracking” setting by default, which prevents embedding any cross-domain content into the main web page for security reasons. This has affected the “Pega Web Mashup” feature, which provides an easy way to embed Pega content into third-party host applications. To resolve this, Mashup has been updated with the recommended webkit to support Safari 13.1+: with these new changes, other browsers will not see any difference but Safari users will need to perform additional interactions prior to the load of Mashup in order to give permission and accept cookies.

INC-129848 · Issue 580458

Refresh handling added for cancel 'add item' while offline

Resolved in Pega Version 8.4.3

When using iPad and iPhone offline, filling in one required field, hitting submit (click action: 'Add item') without filling in a second required field, and then hitting cancel resulted in a blank record being added. Clicking the cancel button first without clicking submit before did not add the item. This was traced to the underlying repeating dynamic layer being refreshed during the submit and adding the record, and has been resolved by adding a refresh for the cancel button process as well.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us