EmpowerID's 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.
Purpose of No Code Flows
The primary purpose of No Code Flows is to enable users to design and implement intricate processes with ease, regardless of their technical expertise. Key aspects of No Code Flows include:
Event-driven automation: No Code Flows can be triggered by various events, such as employee department changes, location moves, or other business occurrences. This ensures that the right actions are executed at the appropriate time in response to specific events.
Time-based actions: Users can define a sequence of actions to be executed at predetermined intervals following the occurrence of an event. For example, when an employee leaves the company, a series of actions can be set in motion, such as disabling their email account, revoking access to corporate resources, and notifying relevant parties.
Flow events: No Code Flows employ flow events as the starting point for each process. Users can define custom events based on their unique business requirements, which provides flexibility in designing tailored workflows.
Flow policies: Users can establish flow policies to govern the execution of No Code Flows, ensuring that processes are carried out in compliance with organizational rules and regulations. Flow policies also provide the ability to revoke access or take corrective actions when necessary.
Benefits of No Code Flows
No Code Flows offer several advantages to organizations by providing a user-friendly solution that simplifies complex processes:
Reduced reliance on programming expertise: By eliminating the need for in-depth coding skills, No Code Flows empower a wider range of users to create and manage workflows, reducing dependency on specialized developers.
Increased efficiency: Automation of repetitive tasks and elimination of manual intervention leads to improved process efficiency, freeing up valuable time and resources for more strategic initiatives.
Enhanced consistency: No Code Flows ensure that processes are executed in a consistent manner, which reduces errors and enhances overall quality.
Scalability: As business requirements evolve, No Code Flows can be easily adapted or expanded to accommodate new processes and workflows.
Elements of No Code Flows
Flow Definitions
Think of a Flow Definition as a set of instructions. It's a container that houses one or more Flow Items, which are steps the system follows to react to a particular event. These definitions help administrators design and oversee their business operations by detailing what happens when specific events occur, such as when an employee leaves the company (a "Person Leaver" event).
Flow Items
Flow Items are the individual tasks that the system performs as part of a Flow Definition. In the example of a "Person Leaver" Flow Definition, these tasks could include actions like "Remove this person from all groups" and "Disable all accounts belonging to this person." Each Flow Item is added to the Flow Definition as a step, instructing the system what to do when a certain event takes place.
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
This specifies the exact task that the Flow Item performs. For instance, the action "Disable Person" would be linked to the Flow Item of the same name. When the system encounters this Flow Item, it will perform the action "Disable Person" on one or more individuals as a response to a specific event.
Item Type Scope
This sets the range for the Item Type Action. For example, "All Accounts for Person" means that the action will be applied to every account owned by a certain person.
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 are triggers that set off a series of actions, defined by the Flow Definitions and governed by Flow Policies. They represent situations or conditions that require a systematic response. Examples could include discovering a new mailbox, or an employee leaving the organization. Each event corresponds to a set of 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
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.