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-A23106 · Issue 251959
Wait enhanced to maintain case status for multiple children
Resolved in Pega Version 7.2.2
A Parent case that was configured to resume when the sub-case reached a particular status using "Pending-ParentCaseResume" was not working as expected if there were multiple child cases for a single parent. This was due to the Wait shape taking the current status of the activator (first child case resolved) instead of the dependency status for which the wait shape should be looking for (subsequent child case), and has been fixed by establishing a new property on the Activator page to hold the dependency status and rely on this while checking if the activator has crossed the desired status.
SR-A43745 · Issue 249270
Copied ticket shapes properly visible on Work Management
Resolved in Pega Version 7.2.2
After correcting a problem with the XML generated by ticket shapes related to work states, attempting to use a copied shape with Tickets resulted in a problem locating new entries in the Work Management Tickets landing page. This was an issue with the ticket details being embedded in the shape pages while the rule references that were created for the tickets in pyModifiers were not updated to match, and has been resolved by adding rule references for the tickets embedded inside the shapes.
SR-A77119 · Issue 255564
Fixed attaching files to pre-existing inflight cases after upgrade
Resolved in Pega Version 7.2.2
After upgrade, loading pre-existing inflight cases and attaching a file generated the error "Trying to save an invalid page: Trying to save an invalid page: page is not valid". This was caused by a missing check for LinkPage.pyMemo in cases where LinkPage.pyCategory is not set, and has been fixed by setting pyMemo from LinkPage.pyMemo.
SR-A23504 · Issue 251757
Value corrections made to "Timeliness by resolving unit" SLA functions
Resolved in Pega Version 7.2.2
After upgrade, reports which relied on the out-of-the-box "Timeliness by resolving unit" function were failing. This was an issue with the Work-Resolve application, which was not correctly carrying values for the three SLA columns "Within Goal", "Past Goal", and "Past Deadline", which has now been fixed.
SR-A86465 · Issue 257770
Updated partial search from the Case Manager portal to return consistent results
Resolved in Pega Version 7.2.2
After upgrade, the search functionality was not working as expected. Launching the Case manager portal to search and then open a case worked, but then searching for another case and opening it resulted in the contents of the first search being displayed again. This was traced to inconsistent results when partial search was used from case manager portal,, and has been resolved by showing all the results (top 20) every time partial search is used from case manager portal, irrespective of the ranking ES provides to the search results (i.e., even if the work id is present in the top 20 or not).