Environments

Pega Platform™ 8.7.3 in Pega Cloud® services 2.23.4

Pega Platform 8.4.4 in Pega Cloud services 2.18.5

Scenarios

Two scenarios report slightly different manifestations of the same problem.

Scenario 1

In your application, you create a screen flow, route it to a work basket, select a screen, and click Submit.

You notice that the case disappears from the screen in the screen flow instead of advancing to the assignment. You must reopen tasks every time the case moves to another screen. You tried to resolve this issue by reconfiguring the screen flow.

In this scenario, the assignments are routed to the work queue. When assignments are routed to a work queue, the confirmation message (Confirm harness) is displayed on screen after submitting the previous assignment. This is expected Pega behavior for screen flows and process flows. The expectation is that when any assignment is routed to a work queue, the confirmation message (Confirm harness) is displayed, and you have to access the assignments from the work queue or by Get Next Work to process it.

 For this scenario, the decision tree PerformCriteria returns false, the parameter CurrentUserHasOwnership is set to false in the activity performAssignmentCheck. Based on the value of CurrentUserHasOwnership, the Perform harness or confirmation message is displayed on the screen.

Scenario 2

In your application, you create a case from another case using Actions > Add work and you create a flow that routes to a workbasket. You create a harness for this covered case. After clicking the Done button to create the case, you notice that when the first screen flow routes to the workbasket assignment, the flow action is not displayed automatically. Instead, you see the message Thank you! The next step in this case has been routed appropriately.

You have selected the following checkboxes on pyStartCase for the first flow of the case and the first flow action, respectively:

Look for an assignment to perform after add

Also consider an assignment in a work queue

But the flow action does not display on the screen automatically.

Solution

The PerformCriteria decision tree needs to be changed according to your enterprise requirements so that the decision tree returns a value of true.

Modifying the PerformCriteria decision tree affects other cases; therefore, be aware of this effect on workbaskets, work queues, and other assignments.

To correct the screen flow behavior for the scenarios described, perform the following steps:

Modify the PerformCriteria decision tree to return a value of true and in accordance with your application requirements.

You can also add another assignment before the assignment that routes the case to the work basket. In the flow action, check the For each option and consider assignments in all workbaskets and work queues.

Related content

Creating a screen flow

Decision trees