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-182724 · Issue 677844

Added empty space handling for tab labels

Resolved in Pega Version 8.7

After upgrade from Pega 6 to Pega 8, tab names were not displaying when rules were opened in Designer Studio. This was traced to empty space in the label which caused the Tab name to show as empty, and has been resolved by updating pzpega_ui_dynamiccontainer to use the trim method to check whether the label is empty or not .

INC-183163 · Issue 676252

Optimized table search updated

Resolved in Pega Version 8.7

Search functionality that can be enabled from tables after selecting the "Optimize" checkbox was not working correctly. This was traced to a potential issue getting the search parameter passed into the activity the section uses, and has been resolved by updating the system to get the element from pega.ctx.dom when pyFlowActionHTML div does not exist.

SR-119657 · Issue 184258

Apostrophe no longer causes truncated values in MutliSelectList controls

Resolved in Pega Version 7.1.8

If an option in a MultiSelectList control contained an apostrophe, the option would be truncated at the apostrophe when the work item was saved. This meant that when the item was reopened, the selected value was not highlighted in control. This was caused by the system building the MultiSelectList control with the standard HTML Select tag and its options elements, which do not encode the special characters like apostrophe while preparing the multi select list control with the values, leaving the browser to take the option value as' till apostrophe' instead of the whole value. To correct this, the value is now encoded using the crossScriptingFilter String API.

SR-126732 · Issue 192781

Corrected button label for JAWS

Resolved in Pega Version 7.1.8

With JAWS accessibility active, when you navigate to a menu button labeled "Other Actions", JAWS says "Menu. To move through items press up or down arrow...O" instead of reading out the title of the button. This was caused by the button being used to show the menu, which added role="menu" to it, and this has been corrected in the button generation RUF.

SR-127513 · Issue 196780

JS error resolved for date control in custom filtering section

Resolved in Pega Version 7.1.8

The Date Picker icon on a custom filter section was not opening the calendar popup unless the clear filter button was clicked. This issue occurred when a summarized report included a chart and had the 'Hide summary data' display option enabled, and was caused by an error in the HTML div function for the popover that used the same name for multiple embedded forms. This has been resolved.

INC-170258 · Issue 645043

Removed unneeded query parameter in UI

Resolved in Pega Version 8.7

When using an Ajax container without a dynamic container, a refresh harness / section event call related to pyBlockUnregisteredRequests was not being properly registered, resulting in a 403 error and the message "Unregistered request encountered ..". This was traced to a "pyDataTransform=" query parameter that was present in the PZPEGA_UI_MICRODC file, and the parameter has been removed to resolve this issue.

SR-119090 · Issue 179954

Progressive Paging Header Alignment Issue corrected

Resolved in Pega Version 7.1.8

On page load, the column headers for repeat grid with expand details did not align with the data when using Progressive Pagination. The root cause of this problem was with the design of Repeat Grids with 'Pagination' and Expand Details involved: the headers for Repeat Grid were created as separate table which failed to synchronize size with the table containing the data. To resolve this, changes were made in the GenerateGridHTML Function.

SR-119090 · Issue 175018

Progressive Paging Header Alignment Issue corrected

Resolved in Pega Version 7.1.8

On page load, the column headers for repeat grid with expand details did not align with the data when using Progressive Pagination. The root cause of this problem was with the design of Repeat Grids with 'Pagination' and Expand Details involved: the headers for Repeat Grid were created as separate table which failed to synchronize size with the table containing the data. To resolve this, changes were made in the GenerateGridHTML Function.

SR-120018 · Issue 182167

Handling improved for additional clicks during Report Definition processing

Resolved in Pega Version 7.1.8

When a Report Definition is used on a grid with filters on some columns, it is possible to click on filter and enter some value there. If there is huge data array, it takes some time for filter to load. If there is a click somewhere else in the grid while the filter is loading, the UI became unresponsive. In order to improve performance, a check has been inserted to verify the status of an asynchronous request and handle it smoothly.

SR-131257 · Issue 201800

Set proper gradient inheritance for Microsoft Internet Explorer tabs

Resolved in Pega Version 7.1.8

A skin rule applied on application to apply style on tabs should have shown the active tab with a white background and the inactive tabs should have had a gradient applied on them, but at run time when using the Microsoft Internet Explorer browser the gradient was applied on all the tabs irrespective of the state. The code has now been updated for this browser to prevent accidently inheriting a gradient from parent tabs

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