Flow Designed is a tool that enables process owners and developers to automate a process without writing code.
The flow is basically consist of a Trigger and sequence of Actions. While the trigger states the conditions that start the flow, the action is a business logic that produces a specific output.
Trigger. A trigger starts the flow either by a record-based or schedule-based condition. In this piece, we will trigger the flow when a record is created our Publication table. Thus, it is a record-based trigger.
Action. As we have mentioned earlier, an action is a business logic that produces a specific output. While there are several built-in core actions in ServiceNow Flow, we have used the Ask For Approval and Send Email actions in this piece. Generally, like the Ask for Approval action below, an action has an intuitive interface designed for a no-code development. Additionally, the flow stores any data gathered or generated an action as reusable variables within the flow, example is the Publication Record that we have set as our trigger.
Flow Logic. Another noticeable component in our first illustration is the “If (Approval State) then” condition. It is called Flow Logic designed to provide us conditional or repeated actions logic.
Spoke Action. We have mentioned earlier the core actions. On top of those, there are as well spoke actions or an application-specific actions.
Testing. Testing our flow before its publication is a recommended practice. The Flow Designer provides us a rich tool for testing.
Hope this helps.
NeuralWorkz 