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-D71355 · Issue 537006

Support added for dynamic CSS class reference in optimized grid

Resolved in Pega Version 8.3.2

When using the property pyStatusWork in an optimized grid, it was not possible to set a color code for different work statuses. This worked on an unoptimized grid. This has been resolved with the introduction of a dynamic CSS feature. This control can be changed to an autogenerated control like "Formatted text" and apply color coding through classes. To use this, a property value must be specified in cell classes in the presentation tab of the table cell, and then populate each result of a data page with that property which contains some class value appropriate for status value. CSS must be written for the different classes (class name is stamped on <td> in markup).

SR-D71402 · Issue 532330

Localization added for Pega Call Login screen

Resolved in Pega Version 8.3.2

Localization has been added to the label "Value can not be blank" on the Pega Call Login screen.

SR-D71522 · Issue 539321

Radio button error resolved for scenario testing

Resolved in Pega Version 8.3.2

When creating a scenario test case that selected a radio button and navigated the screen, it worked to complete a case and save the scenario test case in a rule set. However, attempting to then run the scenario test case stopped with the error message "Value cannot be blank" for the radio button even though the value "No" was captured for the button. This was traced to the firing of the change event, and the system has been updated so 'pega.u.d.setProperty' will only fire a click event on a selected radio button option.

SR-D71756 · Issue 533548

Thread Cleanup error resolved

Resolved in Pega Version 8.3.2

After upgrade, intermittent exception errors were being generated by the FreeClipboard activity when switching between applications. This was traced to specific use-case issues with Thread Cleanup, and has been resolved.

SR-D71944 · Issue 543729

Resolved data page loop in templatized UI

Resolved in Pega Version 8.3.2

A Layout Group was configured with six dropdowns sourced to Parameterized datapages with "disable automatic refresh" unchecked; every next dropdown depended upon the previous property, and the previous property was sourced as parameter, and so on until last dropdown. When the value in the dropdowns changed, the section kept refreshing and the portal became unresponsive. This was traced to the combination of a Datapage as the source to the dropdown with "disable automatic refresh" unchecked and expression evaluation as well.Templatized UI has 'visible when' expressions for all the properties inside the top level page. Changing the first one fired refresh on the next one, and the next one's refresh fired the other drop down refresh until it became recursive. This did not occur in non-templatized UI as it does not have expression IDs and there are no recursive calls. This issue has been corrected by modifying how the temporary mapping is populated by the reloadCells API in Expression Evaluator to prevent unwanted cell refreshes.

SR-D72121 · Issue 536408

Currency Control accepts value on PostValue action set

Resolved in Pega Version 8.3.2

Currency control in the section was sourced by a decimal property. Irrespective of the value entered, the validation triggered the message "entered value is not a decimal value" and did not allow user to proceed. Investigation showed than on getting the server response for post value action, the target element was updated with the response value when it should be skipped for currency control. To resolve this, an additional check for attribute: data-formatting has been added to the textInput control so when action PostValue is configured on Currency control and there is a change of value, the system will skip replacing the value with formatted value.

SR-D73260 · Issue 536888

Multiselect control support for offline-enabled iOS app

Resolved in Pega Version 8.3.2

After a custom mobile application for iOS was built and was running on iPad for an offline-enabled user adding a multiselect control into a section as part a flow caused the screen to hang when a save or submit was performed. This has been resolved by enhancing support for offline multiselect submit with the addition of pzpega_ui_template_multiselect_capsule to offline static bundle.

SR-D73510 · Issue 538662

Cross-site scripting filtering for ActionStringID

Resolved in Pega Version 8.3.2

Cross-site scripting filter logic has been added to the ActionStringID function.

SR-D73847 · Issue 536161

Added exception handler for URL decode error

Resolved in Pega Version 8.3.2

After logging in to Pega Deployment Manager, clicking Users -> People in the left navigation panel resulted ArrayIndexOutOfBoundsException. This was traced to an incomplete trailing escape (%) pattern and has been resolved by adding checks and exception handling for incomplete data from the browser.

SR-D74008 · Issue 537289

AAAFilter on the grid shows value for a second click

Resolved in Pega Version 8.3.2

A Filter on the grid was not showing any record value for a second click. This was traced to a conflict in considering column headers caused by the Filter Icon delegating two Grids, leading the process to take the context of the other Grid instead of the one which had been clicked. To resolve this, a check for the right context of the Grid has been added to the filterOnProperEvent method.

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