INC-128960 · Issue 571360
Corrected approval step task message
Resolved in Pega Version 8.1.9
When a case progressed to the approval step, the task name did not properly appear as part of the "Please approve or reject this" message. In another scenario, a portal which supported locale switching was not translating "Please approve or reject this" when the locale was switched, but instead displayed the message in the original language. Investigation traced this to the pzInstructionsForApproval data transform storing the localized field value, causing it to persist inappropriately. This has been resolved.
INC-131151 · Issue 572832
Resolved empty body for Reject email
Resolved in Pega Version 8.1.9
When using the pzEmailActions Section in Correspondence for Approve/ Reject functionality via email, there was no reply body in the email for Reject Option. This was due to the flow action for the Reject email being different than that of the Approve email, and has been resolved.
INC-131385 · Issue 573454
Swagger APIs updated
Resolved in Pega Version 8.1.9
The Swagger File APIs have been updated to ensure swagger document files generated meet specifications for editor.swagger.io .
INC-134370 · Issue 577635
Expanded Grid locking updated
Resolved in Pega Version 8.1.9
When using pyDashboadMyWorkList to show the cases of an operator with Master Detail in Read Only mode, the system was acquiring a lock on the expanded work object. To resolve this, the following changes have been made: * In activity Assign-pyAcquireObject, If the parameter bRODetails is true, do not call acquireWorkObject and do obj-open-by-Handle to get assignment and work page in pyAcquireObject activity. * In activity acquireWorkObject, the parameter skipWorkLock has been removed as acquireWorkObject should always acquire the lock.
INC-134709 · Issue 579433
Updated endpoint Cross-site scripting protection
Resolved in Pega Version 8.1.9
Cross-site scripting security has been updated for Endpoints in Display activities.
INC-140739 · Issue 592830
UniqueID enhancement for attached files
Resolved in Pega Version 8.1.9
When two files with the same name were uploaded by different users simultaneously through Pulse or if a user uploaded two files with the same name across two sessions, whichever file arrived later was overriding the previous one in the system. As a result, the first pulse post ended up with an incorrect file attached. This has been resolved with an enhancement to add an API that appends a uniqueID to the file before uploading to ServiceExport directory.
SR-D98224 · Issue 580595
Updated endpoint Cross-site scripting protection
Resolved in Pega Version 8.1.9
Cross-site scripting security has been updated for Endpoints in Display activities.
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.