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-184040 · Issue 688255
Improved accessibility for Disclosable Documents/attach files/auto selection dropdowns
Resolved in Pega Version 8.6.4
When using Dragon for accessibility, issues were seen when trying to select different options in the dropdowns related to attaching multiple files. This was caused by the legacy grids being used not supporting this type of accessibility functionality, and has been resolved by updating pzAttachFileDDFileList to use an optimized table instead.
INC-187350 · Issue 703198
UUID added to iOS direct photo upload to differentiate filename
Resolved in Pega Version 8.6.4
When "Content Storage" with the option "Store in repository" was enabled on the "Integration" tab in the Application definition, it was not possible to add more that two attachments to a case with an iPhone when directly capturing a photo through the camera app instead of uploading the photo as an attachment using the gallery. When using the default "Store in Pega database", the additional photos could be uploaded directly from an iOS camera without any errors. Investigation showed that when "Store in repository" was enabled, a file name conflict check was done in the repository. Because the iOS camera app saves/uploads every image as "image.jpg", this caused the error when checking for a filename conflict in the repository. This has been resolved by adding code to append a UUID to the attachname when the device is mobile and browser is Apple Safari.
INC-192673 · Issue 689554
Tab highlighting updated
Resolved in Pega Version 8.6.4
Not all elements were indicated with yellow highlighting when tabbing through the screen. This has been resolved.