3 Major Fundamental blocks in Flow03-12-2018 0 Comment(s)
There are three major components that make up the Flow. Of course, there is a lot for you to learn about the new application, but what I am covering below are the nitty-gritty fundamentals one must know and understand to be able to create workflows using Flow.
Here they are, the three fundamental blocks (components) of Microsoft Flow
Send email when a new email is arrived.
There are two types of triggers:
- Automatic trigger is pre-programmed into the workflow based on a certain rule (i.e. new document or item created, email sent, etc.) Automatic Trigger can also be passed from another application, like PowerApps. For example, at a certain point of the data collection using PowerApps app that you created, a workflow is started to carry the item/data through say an approval cycle. In this case, Microsoft Flow will start automatically from within another application.
- Manual Trigger is a trigger initiated by a user. Unlike with automatic trigger above, the workflow will only start when initiated manually by the end user (for example, from the Document Library for a selected file). Manual trigger is only supported for certain types of workflows (i.e. Get feedback from your manager for the selected file).
An action is something that occurs as a result of the workflow. Below are some examples of the out of the box actions that exist in Microsoft Flow:
A condition is essentially your “If Statement”. If this happens – do this, if that happens – do something else. A classical example is an approval process. If the user approves an item or a document – send an email with approval, if a user rejects – send an email with rejection. Another example could be based on metadata. For example, if you have a Purchase Order approval process and PO dollar value is less than $10,000 – send it to Finance Manager for an approval and POs > $10,000 – send them to CFO (Chief Financial Officer).
No Comments to Show