INC-187350 · Issue 703199
UUID added to iOS direct photo upload to differentiate filename
Resolved in Pega Version 8.7.2
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 706242
Tab highlighting updated
Resolved in Pega Version 8.7.2
Not all elements were indicated with yellow highlighting when tabbing through the screen. This has been resolved.
INC-194180 · Issue 704637
GetChildcases handling updated for large numbers of cases
Resolved in Pega Version 8.7.2
When a very high number of child cases being processed contained a wait shape that was dependent on the movement of a parent case, some of the cases were moved to the next step of the flow automatically while others required a manual command to ResumeFlow. In extreme cases where many child cases were waiting, a node crash could occur. This was traced to the pzGetChildcases report having a maximum value of 500 lines, and has been resolved by increasing the maximum number of rows to retrieve to 9999 in the Data Access Tab of the pzGetChildCases report definition. In addition, the pxCheckFlowDependencies activity has been modified to perform with a higher number of cases, and DSS(MaxRecords) logic has been added to split the child cases into multiple queue items for each access group to decrease load on each thread process.
INC-207218 · Issue 706368
Check added to prevent duplicate approval by single agent
Resolved in Pega Version 8.7.2
When using a cascading Approvals process supported both by a web access button or by responding via email, a single agent could use both methods and advance a case an additional step as if they were the next approval level. This was due to the system only checking the pzInsKey when processing the approval while the assignment key will be the same for the cascading approvals assignments. This has been resolved by introducing a datetime check to validate if the email approval assignment creation datetime and the one in the database have same value; if yes the approval process will proceed and if not it will exit.
INC-207996 · Issue 709664
Check added for parent case dependency if deferred-save is used
Resolved in Pega Version 8.7.2
After updating the status of a parent case to "Pending-ChildCaseDependency", the wait shape for the child case that should have been triggered by the status did not work and the child case remained on hold. This was a missed use case for the pxCheckFlowDependencies activity where defer-save operations on Index-AssignDeps class was not considered, and may happen when the Queue Processor is evaluating the dependencies while instances to Index-AssignDeps are not committed yet. To resolve this, code has been added to check the entry of the parent case dependency in deferred-save if its not present in Index-AssignmentDeps table.
INC-208394 · Issue 713552
Error handling updated for Data-Work-Attach-File
Resolved in Pega Version 8.7.2
If a file is uploaded which has the same name as an existing case attachment or if any issue happens during file attachment, the attachment will fail and an error message is displayed with an option to cancel the operation. However, even if the upload was not successful the related Data-WorkAttach-File instance was created and persisted in the Workattach table. Investigation showed this was caused by the process for persisting the Data-WorkAttach-File record occurring prior to the process that returns the errors, and this has been resolved.
INC-209404 · Issue 710407
MultiFilePath supports file upload with leading special character
Resolved in Pega Version 8.7.2
Updates have been made to the pzMultiFilePath control in order to support uploading a file with a special character such as "%" at the beginning of the name.
INC-210680 · Issue 712071
Updated logic for setting param.PrimaryPage in transfer
Resolved in Pega Version 8.7.2
TransferAssignment was failing intermittently when doing routing either by background processing or manual transfer. Investigation showed this was caused by a null param.PrimaryPage value which resulted in a NullStepPage exception. This has been resolved by adding a Property-Set method just before calling the activity pxTransferAssignment. In addition, the "Require authentication to run" check box in the pxTransferAssignment activity has been set to on.
INC-210787 · Issue 710394
Multiple child case assignments open correctly in Ajax container
Resolved in Pega Version 8.7.2
After configuring two cases with a parent-child relationship, the child case was configured with a parallel process with two assignments. When trying to open the child case assignments in an Ajax container, only the first assignment would open. Investigation showed this was caused by the "reloadAlways" parameter not being sent to openAssignment due to a custom control being used. To resolve this, the reloadAlways has been added as an argument to the OpenAssignment function call in pyAssignmentsLabel.
INC-212896 · Issue 711189
Resume Flow will print Flow Action Label in audit history
Resolved in Pega Version 8.7.2
After calling Resume Flow for processing the assignments, when the Assignment was processed the Flow Action Name was printed on the Audit History instead of Flow Action Label. Investigation showed that in the Complete assignment activity, there was no code in the 'if' loop to set the value of actionLabel. If the value was null, the property set in the next step sets actionLabel to flowActionID and the audit history result is FlowAction ID instead of FlowAction Label. To resolve this, logic has been added in the CompleteAssignment Activity step 5 to set ActionLabel with Flow Action Label.