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-D79103 · Issue 543136

Corrected Finish Assignment error

Resolved in Pega Version 8.3.2

When trying to open a resolved case using the "open assignment" action in a button by passing an assignment key, finish assignment was not working. This was traced to context not being correctly set before querying for the errorDiv for removal, and has been resolved by explicitly setting the current context before removing the errordiv.

SR-D79777 · Issue 542046

Corrected top navigation rendering for Robot Manager harness with parameters

Resolved in Pega Version 8.3.2

When using "Robot Manager", a Single Doc, top navigation enabled portal, with pre DTs or Activities provided to launch a new harness on click of links from multiple places, an invalid data error appeared when a new Harness was rendered as part of some button or link click. If the the tab was closed and the Robot Manager portal was initiated from Dev studio, invalid data was loaded. This was traced to a missing use case for loading the portal center-panel harness when it was configured with preactivity and preDT with parameters. To resolve this, the showdesktop activity has been updated to handle preDT and preactivity parameters of the launch harness action.

SR-D80223 · Issue 542921

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-D81779 · Issue 543855

Logic added to prevent refresh on enter when no action is configured

Resolved in Pega Version 8.3.2

After configuring a text input followed by an icon with display SmartInfo for click action, switching focus to the text input again after displaying the SmartInfo and hitting enter invoked the refresh harness even though no action was configured for the text input. This has been resolved by updating 'pzpega_ui_events.js' -> keyDownHandler() with logic to call preventDefault() based on certain conditions.

SR-D81900 · Issue 544327

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-B71423 · Issue 319981

Localization added to pyAccountSettings field labels

Resolved in Pega Version 7.4

Field label localization for the pyAccountSettings section rule has been added to the Pega-IntegrationArchitect ruleset.

SR-B54277 · Issue 336406

Trimmed unneeded properties from doUIAction call

Resolved in Pega Version 7.4

Null pointer exceptions were generated when relaunching the manager portal after saving a work-object, and the error "Request-URL Too Large. The requested URL's length exceeds the capacity limit for this server" appeared. This was traced to the number of properties included in the doUIAction call; unnecessary parameters have been removed to resolve this issue.

SR-B66164 · Issue 325166

Handling improved for pzActiondropdown's Action label value

Resolved in Pega Version 7.4

When an alternate flow action was picked from LocalAction's list and then submitted, the presence of any page-set messages would cause the submission to fail and the flow remained on the same flow action. This was an issue with handling the changed value of the FlowAction label, and the pzActionDropdown control has been modified to get the correct pyDefaultActionIndex parameter value.

SR-B70422 · Issue 326897

Removed unnecessary add/delete history entries related to empty page properties

Resolved in Pega Version 7.4

The field level auditing configured for page group or list property types was creating multiple add and delete entries in the history of the case even though the pagelist/pagegroup had not been modified. This was traced to method used by the pagelist change audit process to compare current pages to the previous value of the pagelist pages: during pagetostring conversion, sometimes the empty properties in page are present in the String and sometimes they are not, resulting in a difference that generated the non-essential audit entries. This has been fixed by changing the getProperty references in getPageAsString function to use getIfPresent instead. Null checks have also been added.

SR-B70595 · Issue 328754

Out of box REST API creates Page Lists with pxObjClass

Resolved in Pega Version 7.4

Page-Merge-Into was implemented in such a way that the pxObjClass was added for a page but not for a Page List until the case was created. This interfered with validating pagelists and identifying problems with the message data that would allow the case to be rejected before creation. To allow for more flexibility, the pzCreateCaseInternal activity contains an added a property-set so that the pxObjClass is updated on embedded pages.

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