SR-125906 · Issue 192682
Work object locking improved for Advance Flow
Resolved in Pega Version 7.1.8
An Advance Flow call in SLA gave a 'lock not held' error on commit when it was used in subcases where the parent has a dependency (e.g. waiting for the child to resolve). This was a problem where the commit released the work object before the escalation action was executed, and has been resolved by modifying 'SpawnQueueItemForFlowDependency' to open and set the new transaction before and after the commit.
SR-126051 · Issue 188520
External assignment goal execution corrected
Resolved in Pega Version 7.1.8
When an external assignment was created and correspondence generated to provide the external link, using Goal Execution to send a follow up was not working as expected after migration. Previously, the .CorrHandle property was stored and retrieved from the pxflow pages with a reference to the main flow which contained the External Assignment, and the "ExternalGoal" activity used the CorrHandle property to retrieve the correspondence and send a follow up. This was no longer working as the .CorrHandle property was relocated under a different page (VerifySendCorr). CorrUpdate has been modified to handle the flowname properly.
SR-126121 · Issue 189977
Improved Global Search box dismissal on iPad
Resolved in Pega Version 7.1.8
On an iPad, prforming a search with any application that shows the global search control in its header displayed a pop-up that could not be dismissed by tapping on the application below the search box. This issue occured when the script pega_desktop_AppControllerLite.js is included in the header section of the harness.To address the problem, the event binding logic for search on mobile devices has been updated to listen for a tap event instead of a click event.
SR-126368 · Issue 196112
Application Wizard node validation improved
Resolved in Pega Version 7.1.8
When using the new application wizard on a FW which has multiple built ons, selecting cases from a built-on app caused the wizard to validate the classes incorrectly and expected the user to change class names. To correct this, the application express has been updated to track intermediate class nodes that are not class groups, and now tracks non-workgroup and case type leaf name components and aggregates them.
SR-126490 · Issue 190168
Disabled unneeded PEGA0050 alerts
Resolved in Pega Version 7.1.8
PEGA0050 alerts were triggered when a clipboard page list was copied to another list. In general these copies happened when lightweight page lists are involved. In Pega 7, lightweight lists have been enhanced and these copies are not required in most of the cases. Because it is no longer needed, the "alerts/virtuallists/copy" setting has been changed to false to disable the alerts
SR-126545 · Issue 189937
Added remote case handling for password protected implementation applications
Resolved in Pega Version 7.1.8
There was a problem creating an implementation application in Application Express if the built-on application was password protected and the current logged-in application was also password protected, and the cases from built-on have remote case types. This was caused by validation issues, and has been corrected by modifying 'CreateObjectByPage' to pass the parameter 'SkipAddRemote' while calling save activity as true. Save will use this activity to skip current validation through 'ManageRemoteWorkTypesInApplication'.
SR-126587 · Issue 191010
Workbasket name updated in Case Manager portal
Resolved in Pega Version 7.1.8
When CaseManager portal was launched and any particular WorkBasket selected, the text "WORK IN XXXXX WORKBASKET" was shown. XXXXX was the WorkBasket name, which was being picked from RuleName(Identifier) instead of ShortDescription. This was unexpected, and has been changed.
SR-128118 · Issue 191010
Workbasket name updated in Case Manager portal
Resolved in Pega Version 7.1.8
When CaseManager portal was launched and any particular WorkBasket selected, the text "WORK IN XXXXX WORKBASKET" was shown. XXXXX was the WorkBasket name, which was being picked from RuleName(Identifier) instead of ShortDescription. This was unexpected, and has been changed.
SR-127754 · Issue 192902
Modified TransferAssignment to pass SLA parameter with Reassign
Resolved in Pega Version 7.1.8
Assigning the work object configured with an SLA from workbasket to worklist using the out-of-the-box Transfer flow function before the Goal/deadline was reached caused the SLA escalation action to not be triggered when the deadline expired. This was due to the UpdateSLA parameter not being sent when Reassign was called as a post processing activity of the Transfer flow action. This flow action has been deprecated in later releases and replaced by the new flow action pyTransferAssignment, and the ReassignAssignment activity has now been modified to pass the updateSLA param while calling Reassign.
SR-127806 · Issue 195855
Sort by ID enhanced to handle custom ID formatting
Resolved in Pega Version 7.1.8
Sort by ID was not working correctly for workbasket/worklist if the workID was in the format String-Number-Number and not in expected format of either String-Number or String-Number-String. The Pega-RULES:compareWorkIDs function responsible for sorting the workID assumed the ID would be in this format because it used pxRefObjectInsName - an internal property that could not be overridden. However, it was possible to create another property in the "Assign-" class of a custom rule set that could be updated with the value of pxRefObjectInsName by iterating it through the list, and then it could be configured in a grid as sortable row which could further be sorted through a custom sort function. An enhancement has been added to the compareWorkIDs function to handle IDs in the String-Number-Number format with additional handling for 2 part vs. 3 part IDs.