EmpowerID's innovative No Code Flows, also known as Business Request Flows, offer a sophisticated toolset designed to efficiently manage business processes in response to various events. This comprehensive feature set equips administrators with the necessary tools to oversee and automate complex procedures without requiring code-writing expertise. This document provides an overview of the key elements within No Code Flows and their respective functionalities.
The primary goal of No Code Flows is to simplify the management of business processes resulting from specific events. By automating a series of actions, this feature allows administrators to quickly create and implement workflows that react to numerous scenarios without the need for coding.
Essential Elements of No Code Flows
Flow Definitions
A Flow Definition is a logically named container consisting of one or more Flow Items designed to execute sequentially following a specific event. Flow Definitions help administrators create and manage their business operations by outlining the sequence of actions to be performed when certain events occur, such as a Person Leaver event.
Flow Items
Flow Items represent individual tasks or actions intended to be performed within a Flow Definition. For example, within a Person Leaver Flow Definition, Flow Items could include actions like "Remove Non-RBAC Assigned Group Memberships from Person" and "Disable All Person Accounts." When added to Flow Definitions as consecutive steps, these items instruct the system on how to respond to specific events, such as the departure of a person from the organization. Each item is strategically designed to handle a particular aspect of the event response.
Flow Items contain several parameters that together form a directive for the system. These parameters define the specific action to be performed, the target, and the scope of resources it should affect.
Item Type Action
Each Flow Item includes a corresponding Item Type Action, which clarifies the exact task intended to be performed by the Flow Item. For example, an Item Type Action called "Disable Person" is intrinsically linked to the "Disable Person" Flow Item. This connection indicates that when the "Disable Person" Flow Item is detected within a Flow Definition, the system will execute the "Disable Person" Item Type Action on one or more individuals in response to a specific Flow Event.
Item Type Scope
Along with the Item Type Action, each Flow Item also has an Item Scope Type. This parameter determines the domain within which the Item Type Action will execute. For instance, "All Accounts for Person" is an Item Scope Type that signifies the scope of the Item Type action extends to all accounts owned by each person involved in a Flow Event.
Item Collection Query
In addition to Item Type Action and Item Scope Type, Flow Items also incorporate an Item Collection Query. This parameter is an SQL statement that the system executes against specific resource types to gather a set of resources related to the Flow Item, in conjunction with the Item Scope Type. For example, within a Flow Item labeled "Disable All Person Accounts" with an Item Scope Type of "All Accounts for Person," the query retrieves all user accounts owned by the individual who is the subject of the Flow Item.
Flow Events
Flow Events serve as catalysts that initiate predefined sequences of actions (Flow Definitions) governed by distinct rules (Flow Policies). They represent explicit incidents or circumstances within an organization's environment that require a systematic response for efficient management of business processes. Examples of Flow Events include "Mailbox Discovered" or "Person Leaver." Each event represents a unique situation that necessitates specific actions.
Flow Policies
Flow Policies outline which Flow Definitions should be initiated in response to specific Flow Events. They act as rule sets that link specific Flow Events to their corresponding automated actions via Flow Definitions. They can be customized with multiple rules for the same event, allowing tailored responses to various business scenarios, such as executing different procedures for internal versus external leavers.
Examples of No Code Flows in Action
Consider a scenario where a new employee joins the company and needs access to specific applications and resources. Using No Code Flows, administrators can create a workflow that automatically grants the necessary permissions upon detecting the creation of a new user account. The workflow could also send a welcome email with essential information and links to required training materials, ensuring a smooth onboarding experience.
Another example involves automating the process of revoking access for employees who leave the company. A No Code Flow can be set up to trigger upon the deactivation of a user account, subsequently removing the user from all associated groups and revoking their access to resources.
The Benefits of No Code Flows for Businesses
EmpowerID's No Code Flows provide a powerful and flexible solution for managing complex business processes without requiring coding expertise. By offering a comprehensive set of tools and capabilities, administrators can efficiently handle various events and scenarios, ultimately enhancing the overall productivity and effectiveness of their organization.