A shape in a flow represents a task that a user or application completes as part of a business process. By connecting different types of shapes in a flow, you can define the path that a case follows from creation to resolution.
The following table describes all supported flow shapes. Some shapes are not available for screen flows or flows that you update in the case life cycle instead of the Flow form.
Name |
Description |
Icon |
Adds notes or comments to the flow without affecting how the flow runs. |
|
|
Routes a case to one or more reviewers, based on a user name, reporting structure, or authority matrix. |
|
|
If you are using Robotic Process Automation (RPA), identifies the robotic work queue from which a robotic VM retrieves assignments and the automation that the VM runs after retrieving an assignment. |
||
Creates a task in a work queue or worklist so that a user can provide input to the flow. |
|
|
Synchronously connects your application to an external system to send or receive data and waits for a response before moving to the next step in the flow. |
|
|
Attaches a file, URL, or note to a case. |
|
|
Moves the case to a different stage in the life cycle. |
|
|
Creates a top-level case or one or more child cases. |
|
|
Creates a PDF file from a specified section and attaches it to the case. |
|
|
Evaluates an expression or calls a rule, such as a decision tree, to determine which step is next in the flow progression. |
|
|
Returns a list of cases that match the search criteria that are defined in the case type. |
|
|
End |
Designates the end of flow processing. |
|
Asynchronously connects your application to an external system to send or receive data and does not wait for a response before moving to the next step in the flow. |
|
|
Converts a temporary case to a permanent object in the database. |
|
|
Creates a message that is sent to the Pulse social stream. |
|
|
Sends a notification to an iOS or Android mobile device to indicate that an action is required by the user. |
||
Asks the user to answer a simple question, based on the format that you provide. |
||
Runs a single-case data flow that makes decisions or captures responses. |
||
Sends an email to one or more work parties. |
|
|
Sends a notification to users over one or more channels based on the logic defined in a notification rule. |
||
Sends documents for electronic signatures by using the DocuSign service. |
||
Performs the same operation for each item in a list. |
|
|
Sends the case to two or more other flows, both of which must finish before the current flow resumes. |
|
|
Start |
Designates the start of flow processing. |
|
Calls another flow from the current flow. |
|
|
Asks the user to take a survey, based on the format that you provide. |
||
Identifies a group of shapes that are associated with the same organizational unit. |
|
|
Updates the case or all child cases and descendants. |
|
|
Runs an activity to perform processing that does not require user input. |
|
|
Pauses an assignment for a specified length of time or until one or more cases reach a specific status. |