INC-147457 · Issue 621708
Elapsed time in Work History Table includes sub-flow
Resolved in Pega Version 8.4.5
Elapsed times were not captured when an assignment was in a wait shape followed by a utility which set a ticket and moved the assignment to a sub-flow. Investigation showed that when flow execution is in a sub-flow and a ticket is raised, the assignment in sub-flow was removed but audit history was not captured. To handle this scenario, the functions pzCleanSplitForTicket and pzRemoveFlowForTicket have been added, and FlowMethodBody FUA has been modified to include pzCleanSplitForTicket instead of CleanSplit.
INC-149213 · Issue 608519
Email attachments properly displayed in mobile browsers
Resolved in Pega Version 8.4.5
When attempting to use any mobile browser to open the email attachment of a work object, a blank HTML page appeared before the email attachment was shown. The blank page did not appear if the mobile browser was set to use "Desktop mode" or "PC mode". This has been resolved by updating the BAC registration method so that correspondence attachments are properly opened in all mobile browsers and HC apps for all channel types. An additional issue of a blank window appearing on IOS devices that was caused by correspondence attachments opening in a new window instead of opening in the current window has also been corrected.
INC-153801 · Issue 625945
Modified handling for updating SLA on Bulk Agent items
Resolved in Pega Version 8.4.5
While transferring SLA-configured assignments to the work basket using the Bulk Agent in background processing, the assignment handle of the SLA item was not getting updated to the work basket assignment handle. The error "duplicate key value violates unique constraint" was logged. This was due to the system not being able to dequeue the SLA item while it was locked by the Queue Manager as part of the background bulk processing, preventing the assignment handle from being updated on the SLA item. To resolve this, the system will perform a direct database open of the SLA item so the assignment handle is updated.
INC-154778 · Issue 620905
Bulk actions filtering works in Spanish locale
Resolved in Pega Version 8.4.5
Filtering by only case type did not return any results when using the Bulk Transfer functionality with the Spanish locale. Investigation showed that the filter value case type had a field value set, but the localized value was not being checked in the pzPostFilterOperation in step 1 'when' condition. This has been resolved.
INC-159334 · Issue 626762
Handling added for custom attachment method
Resolved in Pega Version 8.4.5
When sending a correspondence using the standard SendSimpleEmail activity, choosing only one attachment from the multiple attachments in the work object by passing the pxLinkedRefTo property from the clipboard page to the AttachmentKeysToSend parameter instead of passing the value to the AttachmentCategoriesToSend parameter successfully sent the message and attached it to the work object. However, opening the correspondence attached to the work object showed the attached file as blank even though the attachment was present in the receiver’s email. Research showed that during the comparison of keys in place of pxLinkedRefTo, pzinskey was used. This caused the comparison to not register as true and the attachments display was skipped. This has been resolved by updating the Data-Corr-Email.Show Html rule to use the pxLinkedRefTo field to find the right attachment. The URL encryption was also updated to ensure the links are functional and attachments can be downloaded.
INC-159624 · Issue 626187
Check added to set class for inheritance if Work- is not present
Resolved in Pega Version 8.4.5
Bulk Action transfer was not working for Assignments from Data class. Investigation showed that when the interest page class inheritance did not contain Work-, flow action pyTransferAssignment was not able to render as it is present in Work- layer. To resolve this, a check has been added to the pyGetRelevantActions so that if the interest page class inheritance doesn't contain Work-, the case class will be set from the workobj page.
INC-160078 · Issue 628838
Work object status correctly set to Resolved after refresh
Resolved in Pega Version 8.4.5
When using the Refresh option from the Other Actions menu before submitting the flow action, the work object status was not updating to Resolved-Completed. Investigation showed that when performing the Refresh action, the RefreshOnConflicts activity created a Clipboard page named LatestWorkPage with a copy of the work object. This page was not removed after use, causing the Resolved-Completed status to be set on LatestWorkPage instead of pyWorkPage. To resolve this, a step has been added to RefreshOnConflicts to remove LatestWorkPage.
INC-161463 · Issue 637999
Case Dependency corrected for different access groups
Resolved in Pega Version 8.4.5
Creating a queue item as part of the case dependency was not working as expected when the access groups of the dependent cases were different. Investigation showed that in this scenario, the logic was looping differently and the DependencyList page in pxCheckFlowDependencies was getting removed. To resolve this, the DependencyList page has been moved so it is processed inside the DependencyList.pxResults loop.
INC-162763 · Issue 646111
Case creation and Save As performance improvements
Resolved in Pega Version 8.4.5
Performance improvements have been made to the getApplicationRuleSetList() function to avoid unnecessary and repetitive database calls.
INC-163154 · Issue 638096
Code updated for bulk actions buttons
Resolved in Pega Version 8.4.5
After upgrade, hovering over the "Filter case" button in pzBullkUpdate and the "Create" and "Clear" buttons in pzBulkAddActions caused them to disappear. The warning "This button generates markup that was used to support the older browsers. It is recommended that you update it to the newer markup" was shown, and an update code button appeared. Some custom rules exhibited the same behavior initially, but worked as expected after updating the code and saving them. This has been resolved by updating the buttons in pzBulkUpdate and pzAddBulkActions with the latest UI technologies used for button control codes.