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-207631 · Issue 701551

Decision Table property chooser made accessible

Resolved in Pega Version 8.7.1

The content of the pop-up "Decision Table property chooser" was not accessible by keyboard navigation. This has been resolved by adding the necessary code for focus inside the iframe.

INC-207632 · Issue 703994

DirtyCheck handling updated for Perform harness

Resolved in Pega Version 8.7.1

In some view scenarios, DirtyCheck was displayed but the "OK/Discard/Save" button unexpectedly closed the case view and returned back to the home page. Investigation showed the DirtyCheck harness was not returning to the appropriate page after the modal screen disappeared, and this has been resolved by changing the "Discard/Save" buttons to an "Ok" button for scenarios where a case is opened in a Perform harness.

INC-208908 · Issue 702171

Placeholder value display made customizable

Resolved in Pega Version 8.7.1

The default place holder value (123,456.78) was displayed for the integer controls even when the placeholder was set to None. This has been resolved by modifying the code to allow customization of the place holder value display. If the "Display value using read-only formatting" option present under editable format is selected and the desire is to show default placeholder for numeric fields, "showDefaultPlaceholderForNumber" with owning ruleset as "Pega-UIEngine" must be created and set to true. If "Display value using read-only formatting" is selected and the default placeholder should not be shown in numeric fields, the DSS should be set to false.

INC-178831 · Issue 680984

Ensured correct context for multi-select

Resolved in Pega Version 8.8

When using multi-select controls, there was an intermittent issue with selecting values using a mouse click. Using the tab key worked as expected. This was traced to the focus being event triggered multiple times so pega.ctx.dom returned undefined values in the second call.This has been resolved by focusing the target element before creation of capsule to ensure the context remains the same.

INC-180100 · Issue 699838

Scrollbar persists for multiselect

Resolved in Pega Version 8.8

Selecting more than 20 values in the multiselect control caused the scrollbar to disappear. This has been resolved by removing a custom popover height calculation.

INC-183966 · Issue 676560

Corrected duplicated select file label reading

Resolved in Pega Version 8.8

When using a screen reader, the select file button label was announced twice on focus. Investigation showed this was caused by the helper text and tooltip having the same content which sounded like a duplicate reading. To resolve this, the text is now differentiated.

INC-183996 · Issue 669645

Step name given heading level for better accessibility

Resolved in Pega Version 8.8

When using the JAWS shortcut for navigating through headings, the Step name was not announced as expected. This was due to the Step name not containing the necessary code for a heading, and has been resolved.

INC-184307 · Issue 673228

Improved accessibility for overflow menu tab

Resolved in Pega Version 8.8

When a tabbled layout group has more tabs than will fit horizontally on the screen, icons appear to the left and right of the visible tabs to scroll through the available tabs along with a drop down list to select from all available tabs. Running the accessibility tool generated an error message for the down arrow button on the right. This was traced to a set tabindex 0 for unfocusable items, and has been resolved by adding tabindex="-1" for the overflow menu.

INC-186072 · Issue 677409

Updated ClientDynamicData HTML Rule

Resolved in Pega Version 8.8

After upgrading from Pega 7 to Pega 8, attempting to open an assignment on the staging environment showed a blank page. This was traced to the system trying to open a declare expression of "PegaComm-" class, and has been resolved by updating the pzClientDynamicData HTML Rule handling for the top level page and enabling the expression calculation checkbox in the Advanced tab of the pyCaseManger7 harness.

INC-186081 · Issue 707804

Report filter popup displays correctly

Resolved in Pega Version 8.8

The filter popup was not displayed on the report column for which the filter was intended. This has been resolved by updating the popover js to fix the overlay issue.

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