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.
...
Elements of No Code Flows
Flow Definitions
A Think of a Flow Definition is a logically named container consisting of as a set of instructions. It's a container that houses 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 , 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 represent individual tasks or actions intended to be performed within are the individual tasks that the system performs as part of a Flow Definition. For In the example , within of a "Person Leaver" Flow Definition, Flow Items these tasks could include actions like "Remove Non-RBAC Assigned Group Memberships from Personthis person from all groups" and "Disable All Person Accountsall accounts belonging to this person." When Each Flow Item is added to the Flow Definitions Definition as consecutive steps, these items instruct a step, instructing 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 responsewhat 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
Each Flow Item includes a corresponding Item Type Action, which clarifies This specifies the exact task intended to be performed by that the Flow Item performs. For example, an Item Type Action called instance, the action "Disable Person" is intrinsically would be 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 of the same name. When the system encounters this Flow Item, it will perform the action "Disable Person" Item Type Action on one or more individuals in as a response to a specific Flow Eventevent.
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 This sets the range for the Item Type Action will execute. For instanceexample, "All Accounts for Person" is an Item Scope Type means that signifies the scope of the Item Type action extends to all accounts owned by each person involved in a Flow Eventaction 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 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 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 for efficient management of business processes. Examples of Flow Events include "Mailbox Discovered" or "Person Leaver." Each event represents a unique situation that necessitates could include discovering a new mailbox, or an employee leaving the organization. Each event corresponds to a set of specific actions.
...
| Macrosuite hidden content macro | ||||||
|---|---|---|---|---|---|---|
|
...
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 expertisemakes process management easier by allowing administrators to automate complex actions in response to specific events without writing a line of code. By offering a comprehensive set of tools and capabilities, administrators can efficiently handle various events and scenarios, ultimately enhancing the their organization's overall productivity and effectiveness of their organization.
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|