Flow Designer flow logic
Summarize
Summary of Flow Designer flow logic
The Flow Designer in ServiceNow allows users to create workflows with conditional and repeated actions using a graphical interface, minimizing the need for scripting. This functionality is essential for automating processes and enhancing efficiency in workflow management.
Show less
Key Features
- Assign Subflow Outputs: Specify data returned by subflows for use in parent flows or other processes.
- Call a Workflow: Execute a published workflow using flow data as input.
- Do the Following Until: Repeat actions until a specified end condition is met.
- Do the Following in Parallel: Run actions and subflows concurrently within isolated logic blocks.
- Dynamic Flow: Identify and execute flows dynamically using runtime data.
- End Flow: Terminate the current flow based on an exit condition.
- For Each: Apply actions to each record in a specified list.
- If: Execute actions based on specific conditions.
- Make a Decision: Utilize decision tables for branching logic, which is more readable than nested conditions.
- Set Flow Variables: Assign and access values using flow variables.
- Try: Continue flow execution in the event of errors.
- Wait for a Duration: Pause actions for user interaction or until a specific time.
Key Outcomes
By leveraging the flow logic options in Flow Designer, ServiceNow customers can build robust workflows that streamline processes, reduce manual effort, and enhance decision-making capabilities. This leads to improved operational efficiency and better resource management within the organization.
Enable flows and subflows to specify conditional or repeated actions. Combine the elements of flow logic to create workflows in a graphical interface with little or no scripting.
The system provides these flow logic options.
| Flow logic option | Description |
|---|---|
| Assign subflow outputs | Specify the data the subflow returns when it completes running. Use subflow output as data for a parent flow or as input for another process. |
| Call a Workflow | Run a published and active workflow from your flow. You can use the flow data as a workflow input. For example, you can specify the current record as a workflow input. |
| Do the following until | Apply one or more actions repeatedly until an end condition is met. You can use the flow data to specify the end conditions. |
| Do the following in parallel | Run actions and subflows in separate paths within an isolated flow logic block. |
| Dynamic Flow | Identify and run a flow or subflow dynamically by using runtime data. Build templates to provide expected inputs for dynamically called flows or subflows. |
| End Flow | Stop running the current flow. Use End Flow within a branch of the flow to specify an exit condition. For example, end the flow when it reaches a specific If flow logic block. |
| For each | Apply one or more actions to each record in a list of records. |
| Get Flow Outputs | Use this flow logic to access flow contexts and derive the runtime values for dynamic flow outputs. |
| If | Selectively apply one or more actions only when a list of conditions is met. |
| Make a decision | You can use the decision table branching logic in situations where multiple conditional paths are required, as an alternative to nested If, Else If, or Else flow logic. For example, if you want to determine what kind of car insurance you need, you can add inputs such as your age, accident history, and car model to the decision table to determine a level of insurance coverage. This logic can save you time and present a more readable format than nested if conditions or switch case statements. |
| Set Flow Variables | Assign a value to one or more flow variables, which store flow data as data pills. Access flow variable values by referring to their data pill. |
| Try | Allow a flow to continue running when an error occurs within a flow logic block. Run a sequence of actions in response to errors within the flow logic block. |
| Wait for a duration of time | Use this flow logic to give your users time to act during automated processes or to wait for a specific date and time to complete actions |
Flow logic inputs
Each flow logic option displays one or more fields that are used to determine its behavior. For example, the Call Workflow flow logic has an input where you are able to select a workflow to run. Use these inputs to define the behavior of the flow and enable optional functionality depending on your needs. See flow logic option documentation for a list of the available inputs and how they control the function of that element.
Flow logic outputs
Flow logic options may also have outputs. These represent information that is returned by the flow logic. For example, the Make a decision flow logic has an output that contains a decision answer record representing the decision reached by the flow. See the documentation for a flow logic option to see definitions for its outputs.