Hi Suresh,

A screen flow presents a sequence of assignments to one user. You can use a screen flow to supplement the workflow in a case by calling it from the Subprocess shape in another flow. 

The following features distinguish screen flows from other types of flows:

• The ability to jump ahead or go back to different entry points in the flow at run time. 
• Routing options that are configured in the Start shape instead of in individual assignments.
• Because one user processes all assignments in a screen flow, you cannot route assignments to different users or to a work queue.
• User actions that are configured in the Assignment shape instead of in a connector.
• A single harness that defines the presentation, such as tabs or nodes in a tree, for every step in the screen flow.
• The ability to branch or call only screen flows that use the same harness.

When considering a screen flow in your application, keep in mind that not all shapes are supported and that a screen flow cannot be designated as a starter flow. 

Regards,

Evita.

Hello,

In Pega, the router logic assumes that work in a screen flow must first be processed by a single user (an Operator ID) and not multiple users; therefore, the default behavior always routes work in screen flows initially to user worklists. You can work around the default behavior and assign a screen flow initially to a workbasket rather than 2 specific users as that is not be possible.

The below PDN post will assist you in routing a screenflow to a workbasket:

https://pdn.pega.com/how-route-initial-screen-flow-workbasket

Thanks,

Gisela