Creating a screen flow
You can use a screen flow to collect information from one user.
-
Create the rule that stores the screen flow.
- In the header of Dev Studio, click .
-
On the Create form, enter values in the fields to define the context of the screen
flow.
-
In the Label field, enter text that describes the purpose of the flow.
- To change the default identifier for the flow, click Edit, and then provide a unique value in the Identifier field.
-
In the Apply to field, press the Down Arrow key and select the class that defines the scope of the flow.
The class controls which rules the flow can use. It also controls which rules can call the flow.
-
In the Add to ruleset field, select the name and version of a ruleset that stores the flow.
-
- Click View additional configuration options.
- Click Standard template for screen flows.
- Click Create and open to open the Flow form.
- Optional:
Customize
the way that the user interacts with the screen flow.
- On the Diagram tab of the Flow form, double-click the Start shape to open the property panel.
- In the Harness field, enter the name of a harness to change the presentation of the screen flow. For example, you can display the steps in the screen flow as tabs or as nodes in a tree.
- Select the Save on last step check box to save the case after all steps in the screen flow are completed. If you do not select this option, the case is saved each time that the user completes an assignment.
- Select the Allow errors check box allow the user to move the screen flow to a different step, even if the current step fails validation.
-
In the
Router
field, enter an activity that determines
which user receives assignments in the screen flow. For example, you can select the
standard
ToDecisionTree
activity to route assignments based on the
value that is returned by a decision tree.
Tip: To route assignments to a work queue instead of a worklist, configure an assignment in the flow that calls this screen flow.
- Click Submit.
- Add shapes to the screen flow to define the different paths that the user can take. For more information about the different shapes that you can use, see Flow shapes.