If your Assignment shape uses the standard rule “Worklist”, and your Router uses the standard rule “ToWorkbasket”, what happens?
-
The flow will not save
-
The flow will be suspended
-
The flow will save, but an execution Java exception will be raised
-
The flow will be suspended, and control will be transferred to the FlowProblems flow
When an Assignment uses Worklist (which expects to assign to an individual worklist) but the Router uses ToWorkbasket (which routes to a workbasket), there's a routing mismatch. Pega saves the flow but raises a Java exception at runtime because the routing destination is incompatible - the flow cannot determine where to place the assignment.
Using "Worklist" as the Assignment shape's routing rule while the Router uses "ToWorkbasket" creates a mismatch in what the flow expects to happen at that point — the flow engine still saves fine, but at runtime this mismatched configuration triggers a Java exception during execution rather than a flow suspension. The flow rule itself is syntactically valid, so it saves without error; the problem only surfaces when it actually runs.