EmpowerID's No Code Flows, also known as or 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.
...
are designed to equip administrators with a user-friendly model for managing complex business processes. These could range from onboarding new staff, overseeing department transitions, or processing employee departures. Such tasks often involve a precise sequence of steps that can be laborious to monitor and schedule within specific time periods. Traditional workflows, while useful for bulk processing, may not provide the level of detail required for these multifaceted operations. This is where No Code Flows excel, offering a comprehensive framework for managing such activities while eliminating the need for coding for administrators.
The traditional approach to creating new workflows can be both time-consuming and resource-intensive. Additionally, the absence of a continuation feature in the event of workflow interruption can result in process inefficiencies. No Code Flows have addressed these issues by providing a streamlined method for executing intricate business processes without the necessity for coding, thereby enhancing operational efficiency.
Components 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.
...
is a comprehensive platform with several components, each crucial for automating business processes. These components include Flow Events, Flow Items, Flow Definitions, and Flow Policies and, by extension, include Business Request Types and Approval Flow Policies. Flow Events define the conditions that trigger the process, Flow Items are the activity steps in the process, Flow Definitions are the templates that define the process, and Flow Policies are the rules that regulate the process. Together, these components empower businesses with the ability to automate their business processes in an efficient and logical way. Let’s take a deeper look at these components.
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 (aka, a "Person Leaver" event).
...
Flow Items
Flow Items are the individual tasks that the system performs as part of a Flow Definitionform the crux of the EmpowerID's No Code Flows feature, representing specific tasks or actions to be performed within a Flow Definition. They are the individual steps triggered by a Flow Event, and each one is designed to handle a particular facet of the event response. 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 Accompanying each Flow Item is an associated Item Type Action, which elucidates the exact task that the Flow Item performsto be performed. 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“Bulk Remove Person Group Membership” might be an Item Type Action assigned to a Flow Item. This action suggests that, as part of responding to a specific Flow Event, the system should remove a person from multiple group memberships.
Item Type Scope
This sets the range for Alongside the Item Type Action, each Flow Item also possesses an Item Scope Type. This parameter determines the range within which the Item Type Action will execute. For example, "All Accounts for Person" means that the action will be applied to every account owned by a certain person“All Non-RBAC Group Accounts for Person” could be an Item Scope Type. This suggests that the “Bulk Remove Person Group Membership” action would apply to all group accounts associated with a person that are not managed by Role-Based Access Control (RBAC).
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 and 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.
In effect, the Flow Item, the Item Type Action, the Item Scope Type, and Item Collection Query collectively form an instruction for the system. They define what action to take, where to apply that action, and the scope of resources it should impact. By stringing together multiple Flow Items within a Flow Definition, administrators can construct complex, automated workflows that respond effectively to various Flow Events.
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.
...
pivotal to EmpowerID's No Code Flows feature, acting as triggers that initiate pre-defined sequences of actions (Flow Definitions) governed by certain rules (Flow Policies). They signify specific incidents or conditions within an organization's environment, prompting a systematic response to effectively manage business processes. When an event is triggered, it is sent to the Flow Event Inbox, which is a queue-like structure that holds the events before they are processed by the system.
Examples of Flow Events might include “MailboxDiscovered,” “AccountTakeover,” or “PersonLeaver.” Each one represents a unique scenario that requires specific actions.
...
Here’s a closer look at each of the above-mentioned examples:
MailboxDiscovered
In the context of managing user identities and resources,
...
discovering a new mailbox
...
is an event that may trigger a series of actions. For
...
instance, you might
...
have a Flow Definition that
...
involves verifying the new mailbox, adding it to certain distribution lists, or
...
setting up appropriate security and access controls. The
...
corresponding Flow Policy would
...
then dictate
...
when and
...
how these actions
...
should occur.
AccountTakeover
The “AccountTakeover” event is a critical security-related trigger. This event could signify a potential unauthorized access or control over an account. On detecting this event, the No Code Flow may involve actions such as suspending the account, notifying security teams, initiating an investigation, or implementing additional security measures. The corresponding Flow Policy would govern the specifics of these reactions.
PersonLeaver
The “PersonLeaver” event is triggered when an individual, such as an employee or a contractor, leaves the organization. In response to this event, a No Code Flow might involve actions like disabling the person's account, removing them from groups, archiving their emails, or revoking access to company resources.
...
Again, a corresponding Flow Policy would
...
dictate the sequence and conditions under which these actions should be executed.
...
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 resourcesWithin the No Code Flows framework of EmpowerID, Flow Policies are the command center that connects specific events to appropriate automated actions, leveraging the power of Flow Definitions.
Flow Policies: The Rule Set
Flow Policies essentially constitute the rule set of No Code Flows. They define which Flow Definitions (i.e., the sequence of Flow Items) should be triggered based on the occurrence of particular Flow Events. The policies allow for multiple rules to be defined for the same event, thereby providing a high degree of flexibility and responsiveness to dynamic organizational needs.
For example, an organization might have different procedures for when an internal employee leaves versus when an external consultant's contract ends. A Flow Policy can be set up for 'internal leavers', which triggers a specific set of Flow Items, like disabling access to certain internal systems. A different policy could be set for 'external leavers', which might include steps to revoke temporary access rights.
...
Customizable to Your Organization's Needs
One of the key strengths of Flow Policies lies in their adaptability to an organization's specific requirements and policies. A company can define a wide range of Flow Policies to respond to numerous different Flow Events, each with its unique sequence of Flow Items defined by the respective Flow Definition. This ensures the appropriate automated response is carried out swiftly and efficiently, aligning with organizational practices and requirements.
Flow Policies and Flow Definitions: A Unified System
Flow Policies and Flow Definitions operate in unison to effectively manage business process orchestration. The Policies determine 'what' should happen in response to a specific event, while the Flow Definitions elaborate on 'how' it should happen. Together, they provide a comprehensive yet simplified, no-code framework for automated task execution.
The concept of Flow Policies, therefore, not only simplifies process management but also ensures that an organization’s response to events is consistent, reliable, and in line with its broader operational policies. As a component of EmpowerID's No Code Flows, Flow Policies represent a step forward in the intersection of process automation and identity management.
Business Requests
A Business Request is generated when an event triggers a flow. It represents a formal request to execute the actions defined in the flow.
Business Request Items
These are the individual tasks or actions that need to be executed as part of a Business Request. They are generated based on the flow definition, and each holds data related to the request, such as request data, assignee ID, and resource ID. Each item is processed independently, in the order defined in the flow. Items at the beginning of the flow are executed first. If an item depends on the completion of another item, it will not be executed until the dependent item is completed.
Approval Flow Policies
If the Business Request is linked to an Approval Flow policies, the request routes for approval based on the assigned Approval Flow policies.
Fulfilment Workflows
Fulfillment workflows define the process that occurs when a request item is approved or rejected. For approval, the workflow specifies how to execute the associated action. For rejection, the workflow defines the process that should occur.
Flow Execution Process
The Flow execution process in a No Code Flow involves the following steps:
The flow initiates with an event, such as “Person Mover.” This event is associated with a resource like a “Person.”
The event is added to the Event Inbox.
The applicable policies determine the flows that need to be run. These flows are then added to the Flow Inbox.
Once in the Flow Inbox, each flow awaits processing.
Upon processing, each flow creates a Business Request. This Request consists of multiple Business Request Items, which are individual tasks to be performed.
Each Business Request Item represents an action to be performed. This could range from adding the resource to a group to disabling the resource.
The sequence and timing of the Business Request Items are managed through the Flow Definition.
Upon completion, each Business Request Item will be sent to the Business Request Fulfillment engine, which will execute the tasks.
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|