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-D28657 · Issue 500585

Corrected Reference value's description in Table

Resolved in Pega Version 8.1.6

When a user was given 'property for value' as an ID and 'property for display text' like a name, launching the portal showed the display text correctly until 'refresh' was clicked, at which time the current section showed the property value instead of the property text. Investigation showed that the parameter string split inside the parameterised data page used as a dropdown source failed in the readonly case. This has been corrected.

SR-D5388 · Issue 461278

Corrected dropdown focus issue with dynamic layouts

Resolved in Pega Version 8.1.6

The focus was not retained on the dropdown field whose property was used in the dynamic layout for the refresh condition. Investigation showed that in pzpega_ui_doc_focus.js, the function "focusNextElement" was setting pega.u.d.gFocusElement set to null after the first load. This has been corrected.

SR-D14630 · Issue 491166

Thread label clipboard issue resolved for work objects using skipDCDataModelUpdation

Resolved in Pega Version 8.1.6

In some cases, when a case ID was opened in Designer studio, its corresponding thread name in clipboard was pxThreadName instead of caseID or workID. Tab labels are handled through the Declare_pyDisplay data page. Investigation showed the child page pyDisplay(Developer) of the parent page Declare_pyDisplay, which was expected to contain pyUIElements for each tab, was missing an element for the tab whose label was shown as threadName. As this error was only reproducible for work objects with the 'skipDCDataModelUpdation' property set as true in the 'pyWorkPage', this issue has been corrected by updating the show-harness activity step-2 so the 'skipDCDataModelUpdation' property value is explicitly copied from primarypage ('pyWorkPage' in this use case) to 'parameterPage'. In addition, an issue with filtering records based on Operator Preferences has been resolved by updating ActivityStatusContentHandler to use a simple Show-HTML of the same "ActivityStatusSuccess" content instead of going through an unnecessary harness execution during activity when there is no session established.

SR-D15428 · Issue 491567

Null check added to resolve non-impacting InvalidParameter exception

Resolved in Pega Version 8.1.6

Creating a child case from the SLA goal activity using the 'AddCovered' activity generated the message "Exception in queue item: cannot be null or blank". The error "com.pega.pegarules.pub.clipboard.InvalidParameterException: cannot be null or blank" was also seen. However, no functionality impact was observed. This has been resolved by adding a null check to the getPortalName method, and modifying the HarnessUIBuilder.java file to add safe checks for whether 'portalName' is empty or not.

SR-D15875 · Issue 486381

Spinner wheel dom correctly cleared after incomplete case closure

Resolved in Pega Version 8.1.6

Incorrect behavior of the spinner wheel during a case search following the browser being closed while a case was open has been resolved by updating pzpega_ui_doc_actionRouter to ensure the wheel dom is correctly cleared.

SR-D28469 · Issue 499089

Corrected exceptions report appearing on user screen

Resolved in Pega Version 8.1.6

When "Break on all exceptions" was enabled, the exceptions report was visible on the end user screen when using IE11. This has been resolved with updates to the 'pzpega_ui_dynamiccontainer' and 'pzpega_ui_doc_tabsupport.js' files.

SR-D28480 · Issue 499085

Corrected exceptions report appearing on user screen

Resolved in Pega Version 8.1.6

When "Break on all exceptions" was enabled, the exceptions report was visible on the end user screen when using IE11. This has been resolved with updates to the 'pzpega_ui_dynamiccontainer' and 'pzpega_ui_doc_tabsupport.js' files.

SR-D8790 · Issue 487287

Corrected thread cleanup logic for doUIAction in WorkCover

Resolved in Pega Version 8.1.6

When accessing a case from the worklist or opening the case from worklist and refreshing the case by pressing F5, clicking Approve resulted in a java.lang.NullPointerException error. Investigation showed that the "pyWorkCover" page that the section was running on was being removed in the top navigation portal / SDM portal as part of the thread cleanup logic in doUIAction. This has been corrected.

SR-D13569 · Issue 491716

Additional parameter format added for multiselect controls

Resolved in Pega Version 8.1.6

Attempting to pass a parameter like "Value1", "Value2" to a data page used for the MultiSelect Control was not working even though the same format worked for autocomplete control. This was an issue where the flow of fetching the data differed between the two controls, and support for this parameter format has now been added for multiselect controls.

SR-D5413 · Issue 484329

Enhanced returned value handling for using Expand when in collapsible dynamic layout

Resolved in Pega Version 8.1.6

After configuring an 'expand when' condition with the intention that the dynamic layout expands when the user doesn't enter the required field(@hasMessages(Primary)), the dynamic layout was expanded by default even though the "Expanded on load" was not enabled. This was traced to 'expand when' not getting set on refresh due to a different returned value for the condition, and has been corrected.

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