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-129232 · Issue 197812

LiveUI inspector enhanced to uncover elements inside non-Live UI frames

Resolved in Pega Version 7.1.8

Issues were found with inspecting elements inside non-auto sections from Live UI; Live UI inspector did not point to the relevant UI component, but rather pointed to the header level, causing frames inside an iframe without Live UI Code to be ignored even if they did have elements that could be inspected by Live UI. In order to ensure all elements are caught, code changes have been inserted to loop over all child frames and recall itself with the next frame to cover all elements that can be inspected by Live UI.

SR-129249 · Issue 194654

Accessibility added to pxDataField and VisualizeAttachingScreen

Resolved in Pega Version 7.1.8

Accessibility has been added to the out-of-the-box functions pxDataField and VisualizeAttachingScreen.

SR-129423 · Issue 198808

Updated responsiveness for certain dynamic column widths

Resolved in Pega Version 7.1.8

At run time, the width of a dynamic layout in a section was not changed as per the transformation and responsiveness was not working as expected for specific column widths. This was an issue with Skin CSS generation for dynamic layouts in generating column widths when another format was applied at a breakpoint, and has been resolved.

SR-129461 · Issue 196393

Security enhanced for RunActionWrapper

Resolved in Pega Version 7.1.8

A potential XSS vulnerability was detected and resolved in the RunActionWrapper.

SR-129465 · Issue 196346

Corrected parameter clearing in MultiSelect control

Resolved in Pega Version 7.1.8

After selecting any value through multiple select and saving it, the saved data was not present when the case was reopened. In Multiselect control, previous values were also being added. This was an issue where parameter values were not being correctly cleared after being used in the MultiSelectList control, and has been fixed.

SR-129525 · Issue 198580

Button question display style now defaults to inline

Resolved in Pega Version 7.1.8

If a question that is marked as required is very long, the asterisk mark was distorted on the radio button label and came up at the extreme end of the label as a separate entity rather than at the end of the label. This was due to the display style for icon required class being set to inline-block instead of simply inline. As the inline display is more appropriate for this field, the default style has been changed to this.

SR-129537 · Issue 195268

Corrected button highlighting for error in selecting required values

Resolved in Pega Version 7.1.8

The Required field label should be highlighted in cases where the value is not selected for the required fields, but the first option of the radio button was being highlighted instead. This was due to misplaced CSS, and has been updated to use the proper label for value to highlight field label in case of error.

SR-129611 · Issue 197287

Corrected CheckPrivilege function in BulkAssign

Resolved in Pega Version 7.1.8

The RUF pxCheckPrivilegeInWorkClass (called from OpenAndLockWork) was changing the name of the newAssignPage, causing downstream failure of pzBulkProcessItems. The error occurs when a Bulk Transfer operation is performed and the user does not have the proper Role, resulting in a call to the canPerform Access When Rule that then led to pxCheckPrivilegeInWorkClass changing the name of the step page. To fix this, the parameter will be assigned to the "newAssignPage" or primary page in the OpenAndWorkLock activity.

SR-129722 · Issue 197103

Removed extra white space in Microsoft Internet Explorer 8

Resolved in Pega Version 7.1.8

When using the Microsoft Internet Explorer 8 browser, extra white space appeared above the 'next' button when declare expression was fired in a screen flow which grew with each declare firing. This has been corrected by updating the last condition to check for the 'display' property.

SR-129723 · Issue 200683

Added ability to customize pyMessageKey column of a history record

Resolved in Pega Version 7.1.8

In order to allow customization of the pyMessageKey column of a history record, it is now possible to call the extension activity pyAddWorkHistoryDefaults in Flowvwhen the work page is not null.

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