SR-127452 · Issue 192406
Case match duplicate check resolved
Resolved in Pega Version 7.1.8
A case match rule to check for duplicates with adding an expression in weighted condition was giving a runtime error due to incorrect page referencing in java step of activity 'RunDuplicateCasesReport' that was attempting to obtain the property from the RD page (which was using a different structure). The page reference has been updated to correct this issue.
SR-130208 · Issue 198155
Handling added for step page call to DeleteAssignment
Resolved in Pega Version 7.1.8
After upgrade, the pxDeleteAssignment with step page Assign-Workbasket was not working as expected. The error was traced to the 'DETERMINELOCKSTRING' activity being available in Work- class while the local customization was passing the Assign- page as the steps page. Handling has been added for cases when the activity gets called on a page other than primary work page.
SR-130526 · Issue 200786
Modified 'save as' to update workgroups across nodes
Resolved in Pega Version 7.1.8
On a multi-node environment, 'Bulk Actions' was not showing all of the workbaskets after a product rule with a workbasket data instance was imported to one node and not others. This was a lookuplist cache issue caused by 'save as' not updating the workgroups, and has been resolved.
SR-130751 · Issue 198798
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-132538 · Issue 201237
Updated RD handling for WorkBasketAssignments
Resolved in Pega Version 7.1.8
After upgrade, if the Assign-WorkBasket pyWorkBasketAssignmentsDefinition report definition included the WHERE criteria .pxSystemFlow== 'FALSE', workbasket assignments for existing cases were not displayed in the harness. This was due to the new PXSYSTEMFLOW column in the pc_assign_workbasket DB table not properly handling this criteria, and a check has been added to resolve this.
SR-129239 · Issue 200337
Added handling for Flow not at Task error
Resolved in Pega Version 7.1.8
Flow not at task and flow removed errors were appearing sporadically. This happened when the trigger fired off the commit inside the post-processing called CorrUpdateNoWO and returned a stale copy of the Workobject, and was complicated by an assumption that was trying to iterate over "pzInternalCaseFlow". This has been addressed in the CORRUPDATENOWO activity.
SR-131217 · Issue 199744
Stopped unexpected trigger caused by attaching note with gadget
Resolved in Pega Version 7.1.8
Declarative rules were being fired every time a note was attached to a work object using the "Notes" gadget (not advanced notes link). To fix this, the pxAttachNote activity has been updated to not trigger the declarative chaining in this scenario.
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.