INC-200936 · Issue 703345
SFTP support added to ValidateURL rule
Resolved in Pega Version 8.5.6
SFTP has been added to the list of schemes which are accepted as part of the validation in the pxValidateURL rule.
INC-202562 · Issue 701629
Updated FieldLevelAuditing logic for page comparison
Resolved in Pega Version 8.5.6
Optimistic locking was resulting in orphan assignments and the error "Error: Flow Not At Task, Error: Flow Removed". In addition, Get Next Work was causing duplicate Field Level Auditing records. This was traced to a missed use case in the logic used in pxFieldLevelAuditing where previousPage and PrimaryPage are compared to see whether they are equal or not, and has been resolved by adding one more condition to mark previousPage as null when the update date time or commit date time are not updated as part of processing.
INC-202943 · Issue 700195
WorkLink URL generation updated for security
Resolved in Pega Version 8.5.6
When using a WorkLink in an email, clicking the link and entering credentials on the login screen resulted in a 403 unauthorized error. This was due to a WorkLink URL generation issue caused by the non-encryption of the RedirectAndRun activity call in the URL, and has been resolved.
INC-204676 · Issue 699111
Localization added to subject line for SendEmailToAssigneeOnGoalTime
Resolved in Pega Version 8.5.6
When a Callback case was created and the assignee notified by email, the subject line was not localized. This has been corrected.
INC-207218 · Issue 706370
Check added to prevent duplicate approval by single agent
Resolved in Pega Version 8.5.6
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-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.