Flow Designer Overview Flashcards
What is the non-technical interface that enables process automation capabilities known as flows?
Flow Designer
What are the benefits of Flow Designer?
- Centralized: provides a single environment to build and visualize business processes
- Robust: provides config and runtime info to create, operate, and troubleshoot flows from a single interface
- User-friendly: provides natural language descriptions of flow logic
- Repeatable: promotes process automation by enabling subject matter experts to develop and share reusable actions
- Scalable: allows extending flow content by subscribing to IntegrationHub or installing spokes
When is it recommended to use Flow Designer?
- To orchestrate business processes across services with little technical user knowledge
- To reduce scripting to simplify upgrades and deployments
- To integrate with 3rd party systems
When is it recommended NOT to use Flow Designer?
- There is existing logic already developed using ServiceNow workflow editor
- ServiceNow instance is running Jakarta or prior version
How to access Flow Designer?
All > Process Automation > Flow Designer
Which roles are required to perform certain Flow Designer functions?
- flow_designer
- flow_operator
- action_designer
What can we create when pressing the + New button in the Flow Designer Interface?
- Flows
- Subflows
- Actions
What does a flow consists of?
- A trigger
- One or more actions
When does a flow execute the action(s)?
When the conditions of the trigger are met
What is a flow action?
- An action is a reusable operation that enables process analysts to automate Now Platform features without having to write code
- Actions are strung together to make a flow
What are the 3 elements triggers can be based on?
- Record-based
- Schedule-based
- Application-based
How does a record-based trigger work?
Record-based triggers run a flow after a record has been created; updated; or deleted
- The triggering record can be used later in the flow as input for actions
How does a schedule-based trigger work?
- Scheduled-based triggers run a flow at a specified date and time: daily; weekly, monthly
- The execution time can be used as an input for actions in the flow
How does an application-based trigger work?
Application-based triggers are added when the associated application spoke is activated.
For example, when an item is requested from the Service Catalog, a flow is triggered
Sometimes, a plugin might need to be activated
What are Flow Actions?
Actions are reusable operations executed by Flow Designer
Examples of actions:
- looking up a record
- updating a field value
- requesting an approval
- logging a value