INC-213654 · Issue 726002
Logic added to skip FLAudit class during compliance check
Resolved in Pega Version 8.6.5
An application compliance error was seen related to classes starting with FLAudit, which are created as part of field level audit history for the classgroup validation. This has been resolved by adding an extra condition to the Rule-Obj-Class-.Validate activity to check if inheritance is from "FLAudit-" class, and if so to skip them as their purpose is similar to History- classes which are ignored for the class group validation.
INC-215354 · Issue 712665
Data- flow actions working in Bulk Process
Resolved in Pega Version 8.6.5
When trying to render a flow action whose 'applies to' class was inherited from Data-, an error was generated indicating that the flow action could not be found. This was traced to non Work- flow actions not being correctly populated, and was an inadvertent side effect of work done to set class for inheritance if Work- is not present. This has been resolved by updating the pzPreBulkProcessModal activity to set the TempWorkPage class to Work- only if .pyActionName is pyTransferAssignment.
INC-215499 · Issue 714489
Assignment routing updated for swimlanes
Resolved in Pega Version 8.6.5
Routing options were not working for workbasket routing when using swimlanes. Investigation showed that when an assignment was added inside the swimlane, the assignment type value was defaulting to Worklist on submit of the assignment property panel. Manually changing it to workqueue did not make the routing section visible. This has been resolved by adding a 'visible when' condition to the "Route To" field to check if the assignment is not in the swimlane. The same check has been added to a 'disable when' condition for the 'Assignment type' drop down.
INC-216406 · Issue 723284
Attachment preview works for filenames with special characters
Resolved in Pega Version 8.6.5
Attempting to preview attachments from the file and attachments view was not working if the file name had special characters. The browser console showed errors complaining that an unrecognized character was present. This has been resolved by adding crossScriptingFilter to sMemo to allow special characters in the attachment preview filename.
INC-188469 · Issue 714843
Updated retainLock for DoClose activity
Resolved in Pega Version 8.8
After sending an external email notification from a case, attempting to use the "close" button resulted in an access denied error. This was traced to a missed use case for recent security improvements which resulted in not setting the required parameter retainLock for the DoClose activity, and has been resolved.
INC-192673 · Issue 689552
Tab highlighting updated
Resolved in Pega Version 8.8
Not all elements were indicated with yellow highlighting when tabbing through the screen. This has been resolved.
INC-194180 · Issue 704636
GetChildcases handling updated for large numbers of cases
Resolved in Pega Version 8.8
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-201723 · Issue 719854
Audit message displays correct parameter value
Resolved in Pega Version 8.8
The Audit message showed "{1}" instead of displaying the parameter value dynamically. This was traced to the pyInstructions field value which contained the message "Please approve or reject this {1}", and has been resolved by updating the pzInstructionsForApproval rule so the correct value is displayed.
INC-203595 · Issue 702360
Updated retainLock for DoClose activity
Resolved in Pega Version 8.8
After sending an external email notification from a case, attempting to use the "close" button resulted in an access denied error. This was traced to a missed use case for recent security improvements which resulted in not setting the required parameter retainLock for the DoClose activity, and has been resolved.
INC-207218 · Issue 706367
Check added to prevent duplicate approval by single agent
Resolved in Pega Version 8.8
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.