SR-124245 · Issue 188290
Clarified handling of unlocked work objects in multinode environments
Resolved in Pega Version 7.1.8
Release lock was not working correctly on a multinode environment. When trying to release the lock from same operator different requestor from different nodes, the error "Unable to unlock this work object" was generated. In a multinode environment, system pulse takes time to update the cache across the nodes, hence the option is not effective immediately. Messaging has been updated to reflect this delay. Once System pulse executes then other requestor will be able to work on this item.
SR-124313 · Issue 190024
FCM remote case type function restored
Resolved in Pega Version 7.1.8
FCM (Federated Case Management) has a button to discover remote case type, but attempting to use it out-of-the-box generated the error "Remote System is not available. Please check the settings". This was due to a lack of authentication in the Service HTTP rules CaseManagement, and the authentication requirement has been removed.
SR-124385 · Issue 187273
Clicking checkboxes smoothed for Bulk Processing
Resolved in Pega Version 7.1.8
While performing Bulk Processing, if the checkboxes used to select items for processing were marked in rapid succession, not all of the selected items were processed by the bulk action. This was due to the timing of the refresh on the boxes, and this has been adjusted so all boxes are refreshed by a refresh list instead of post value process.
SR-124385 · Issue 193689
Clicking checkboxes smoothed for Bulk Processing
Resolved in Pega Version 7.1.8
While performing Bulk Processing, if the checkboxes used to select items for processing were marked in rapid succession, not all of the selected items were processed by the bulk action. This was due to the timing of the refresh on the boxes, and this has been adjusted so all boxes are refreshed by a refresh list instead of post value process.
SR-125377 · Issue 187816
Flow name labels draw from proper cache
Resolved in Pega Version 7.1.8
A flow name label was taking the short description of the starting flow in the class group and appending the class names to it after the parenthesis. This has been corrected by ensuring the code is fetching from the correct cache to populate the label.
SR-125417 · Issue 188362
Timezone handling corrected for Locale Settings tool
Resolved in Pega Version 7.1.8
When the Locale Settings tool was opened, the time zone was always shown as Etc/GMT+12 and did not reflect the current operator time zone. The time zone used is correctly amended based on the option chosen, but the 'selected' option in the select HTML code was not set to correctly reference the actual option selected. This has been fixed by adding a check to set the time zone from the step page if it does not exist in the recurrencedetailspage.
SR-125769 · Issue 188698
ToolTip added for column filtering in bulk allocation
Resolved in Pega Version 7.1.8
While using bulk allocation, filtering a column resulted in reducing the number of results but it was unexpected that the select count was not similarly updated. The count is populated by pre-processing activities and not by the grid, but this information was not clearly conveyed. A Tool Tip has been added for SelectionIgnoresGridFiltering to clarify the usage of the "Select All xx Results" checkbox.
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.