MS flow.docx
Download as DOCX, PDF0 likes24 views
Microsoft Flow is a cloud-based workflow engine that allows users to create no-code cross-application workflows as part of the Office 365 E3 suite. It features a flow designer, various connectors, triggers, actions, and supports complex scenarios such as branching and error handling. Users can create flows through a web or mobile application, utilizing standard, premium, or custom connectors to integrate different services.
MS flow.docx
- 1. Getting Started With Microsoft Flow Microsoft flow is a cloud-based workflow engine, Using Flow end users can create cross application workflows (no code workflows). Flow is a part of office 365 E3 suite. It is a successor of SharePoint designer workflows. Complex level Flows can be promoted to an Azure logic app.
- 2. Microsoft Flows Vs SharePoint Designer Workflows Anatomy of Microsoft Flow Flow Designer Connectors, Triggers & Actions Variables & Data Flow Expressions Branching, Error Handling & Scopes
- 3. Flow Designer – Create a Flow from Browser or Mobile Application Desktop Version Go to https://flow.Microsoft.com Sign-in with Office 365 Account Start from existing template or import from disk or create from scratch (both in desktop & mobile browsers) Mobile Version Install flow mobile app, sign in Create new flow (template or from scratch).
- 4. Connectors Connectors Wrapper around an API that allows Flow to talk with other services.It exposes Triggers & Actions. Standard Connectors – included as part of E3 Microsoft Connectors (SharePoint, Azure Blob storage, SQL Server.) Non-Microsoft Connectors (Twitter, Slack.) https://us.flow.microsoft.com/en- us/connectors/?filter=&category=standard
- 5. Premium Connectors – additional cost Microsoft Connectors (HTTP with Azure AD.) Other Connectors (Salesforce, MySQL.) https://us.flow.microsoft.com/en- us/connectors/?filter=&category=premium Custom Connectors – additional cost , development ISV, System Integrators, End users can create custom connectors to integrate any system/application/service. https://us.flow.microsoft.com/en- us/connectors/?filter=&category=custom Triggers Run based on user action or event From other apps in office 365 – PowerApps, SharePoint, etc. From SQL From dedicated Flow button Run on a schedule
- 6. Flow also run based on time schedule, From every minute to 1 am on Days. Run by HTTP GET/POST to URL generated by flow Call another Flow Call from any application/service/HTTP calls
- 7. Scenarios & Types of Triggers Triggers - Scenarios Simple: Flows start with a Trigger. Advanced: Flows can have more than 1 trigger (async actions) Custom: Flows can have custom triggers Types Polling Trigger Periodically checks the service Checks count as executions Push Triggers Listen for data on an endpoint or wait for event. Actions Execute CRUD operations with workflow context SharePoint: Create Item, Delete Item, Create File. SQL: Insert Row, Update Row, Delete Row, Get Row.
- 8. Transform Data Inline – using expressions (e.g. string operations, math operations.) Other services – Html to text. Send Notification Send mobile notification, send email notification etc. Call other Flow Chain Flows to create complex Flows.
- 9. Variables Use Variables connector* Initialize & then set value Supported value types (Boolean, String, Object, Array, Float). Variables are NOT always necessary! Why variables are not always necessary? Data Flows from each step and is available for all later steps ‘Add Dynamic Content’ allows us to select outputs from previous steps
- 10. Certain outputs show up based on the types of the inputs and outputs. Expressions Expressions can be used in most of the fields to transform data inline IntelliSense available as you type
- 12. Switch For-Each By default, parallel Parallel (20 exec) Supports sequential
- 13. Do-Until Emulate State machines Help in approvals & more Parallel branches Error Handling Actions can be set to run if previous action fails/times out.
- 14. Scopes Logically group actions Allow advanced error handling for a group of actions Scope boxes are in brown boxes.