Creating a screen flow
Create a screen flow to walk a single user through a series of screens to collect information. By dividing information into multiple screens, you provide a well-organized and user-friendly interface that is convenient to navigate.
For example, in an application to book medical appointments, you can create separate screens for patients to enter their personal details, their medical history, and a description of their current issue. As a result, the patient interacts with logically organized information.Screen flow is a type of process. For more information, about processes, see Types of processes.
- Create the rule that stores the screen flow:
- In the header of Dev Studio, click .
- In the Label field, describe briefly the purpose of the screen flow.
- Optional: To change the default identifier for the screen flow, click Edit, and then provide a unique value in the Identifier field.
- Click View additional configuration options, and then select Standard template for screen flows.
- In the Context section, select an application layer to store the screen flow.
- In the Apply to field, press the Down arrow key, and then
select the class that defines the scope of the screen flow.The class controls which rules the screen flow can use, as well as which rules can call the screen flow.
- In the Add to ruleset field, select the name and version of the ruleset that stores the screen flow.
- Click Create and open.
- Open a dialog box with screen flow configuration by double-clicking the Start shape.
- Optional: To provide a unique name for the Start shape, in the Start Shape field, enter a new value.
- In the Start section, define how an application displays the
screen flow:
Choices Actions Apply a harness that you associate with a case type In the Harness list, select Use case type policy. Display navigation to screens as tabs - In the Harness list, select Custom.
- In the Harness name field, press the Down arrow key, and select TabbedScreenFlow7.
Display navigation to screens as a tree view - In the Harness list, select Custom.
- In the Harness name field, press the Down arrow key, and select TreeNavigation7.
Apply your custom harness - In the Harness list, select Custom.
- In the Harness name field, press the Down arrow key, and select your custom harness.
- Optional: To save a case after the last step in a screen flow is complete, select the
Save on last step check box.If you leave the Save on last step check box clear, the case saves information each time a user completes an assignment. As a best practice, save the case data on the last step to avoid performance issues.
- Optional: To allow users to move to the next assignments in a screen flow even if an assignment
fails validation, select the Allow errors check box.
- In the Status section, in the Work status field, press the Down arrow key, and then select a status that a case obtains when the screen flow starts.
- In the Routing section, in the Route to
list, determine a user that completes the screen flow:
- To assign the screen flow to a user who currently processes the case, select Current user.
- To assign the screen flow to another user in your application, select
Specific user, and then configure the user parameters.
You can assign the screen flow to a user by user name or user reference, the reporting manager of the user who currently processes the case, or a case participant.
- To assign the screen flow to a team that shares a work queue, select
Work queue, and then select a team.
A user who picks up the assignment from a work queue needs to complete an entire screen flow.
- To assign the screen flow to a worklist or a team that shares a work queue, select
Custom, and then in the Router field,
enter a router activity to route the assignment.
For example, you can route a screen flow to an external work queue.
- To automatically determine a user at run time, select Use business logic, and then in the Decision tree field, enter a decision tree that returns a user to complete the screen flow.
- Click Submit.
Previous topic Keyboard shortcuts for flows Next topic Changing the path of a process