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.
INC-215354 · Issue 712664
Data- flow actions working in Bulk Process
Resolved in Pega Version 8.7.2
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 714487
Assignment routing updated for swimlanes
Resolved in Pega Version 8.7.2
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.
SR-129197 · Issue 197995
Fixed Silverlight "Create Word Document" error
Resolved in Pega Version 7.2.1
A Silverlight issue appeared while using "Create word document". The older flow action CreateMergedWordDoc was running on the Current Page Context and had a reference to the Word Template used in the PegaSample application. To resolve this, the new Flow Action 'pyCreateWordDocumentCMGallery' has been created. This runs on the pyFlowActionTestPage page and uses the new Word Template pyCMTemplate which has limited set of related properties.
SR-A11534 · Issue 227038
ExecuteSLA activity modified to avoid requeue errors
Resolved in Pega Version 7.2.1
When a broken process SLA was requeued, it went back into the broken queue because the underlying problem assignment was never marked as repaired on requeue. When execution of SLA fails, the assignments are marked as problem assignments in ExecuteSLA activity. The ExecuteSLA activity has now been changed to avoid creating a assignment error by instead using Obj-Cancel to roll back the assignment submission so items can be requeued directly from the SMA portal.
SR-A11665 · Issue 229766
Fixed Bulk Process deselecting some sorted items
Resolved in Pega Version 7.2.1
In Internet Explorer using Bulk Processing, after selecting a column to re-order and several individual items resulted in unexpected checkbox results where certain selected items were deselected and not processed. These items could later be processed individually. The logic has been updated to ensure proper checkbox handling with all browsers.