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.
INC-186072 · Issue 678753
Updated ClientDynamicData HTML Rule
Resolved in Pega Version 8.7.2
After upgrading from Pega 7 to Pega 8, attempting to open an assignment on the staging environment showed a blank page. This was traced to the system trying to open a declare expression of "PegaComm-" class, and has been resolved by updating the pzClientDynamicData HTML Rule handling for the top level page and enabling the expression calculation checkbox in the Advanced tab of the pyCaseManger7 harness.
INC-188141 · Issue 678158
PD4ML upgraded
Resolved in Pega Version 8.7.2
Issues with PDF generation have been resolved by upgrading PD4ML to version 4.0.13.
INC-188644 · Issue 708959
Autocomplete cancel closes correctly
Resolved in Pega Version 8.7.2
Clicking on an autocomplete field and navigating to the next tab without selecting any values caused the autocomplete results to be displayed in the next screen until there was a click or an action was performed in that screen. This was due to the autocomplete not closing correctly, and has been resolved by removing the event.cancelBubble setting.
INC-190233 · Issue 675485
Production check removed for Get Action Details API
Resolved in Pega Version 8.7.2
After creating an assignment for a case and calling the Get Action Details Applied Assignment API, the name tag for views was not included in the returned JSON. This has been resolved by removing a check for production level.
INC-190855 · Issue 681092
Duplicate items resolved for questionnaires
Resolved in Pega Version 8.7.2
When there was only one question page for a questionnaire, the question page title was being displayed twice and the breadcrumb showed duplicate steps. When there was only one step in the screen flow, the survey navigation was hidden. This has been resolved.