EmpowerID's No Code Flows system integrates Flow Policies as a key element to link events with automated actions. These policies use Flow Definitions to activate certain sequences of Flow Items in response to various Flow Events. The system's flexibility lies in its ability to adapt to diverse organizational needs through customizable rules. For instance, a company can handle different scenarios, such as an internal employee exit or the conclusion of an external consultant's contract, by establishing distinct Flow Policies for each case, with specific scopes and actions.
Steps for Creating Flow Policies
The following steps outline the process of establishing Flow Policies in EmpowerID:
Creating the Flow Policy:
Begin by initiating the policy within the EmpowerID system. This is where you define what the policy is intended to do and which events it responds to.
Specifying the Scope:
After creating the policy, define its scope. This involves selecting the specific objects or scenarios the policy applies to. It's important to note that a policy can encompass multiple scopes, allowing for varied applications within a single policy framework.
Procedure
Step 1 – Create the Policy
Navigate to the Find Business Request Flow page by expanding the Low Code/No Code Workflow section and selecting No Code Flow Event Policies from the navbar.
Click the Add New button.
Enter the details for the Flow Policy:
If This Event Happens – Select the Flow Event for the policy.
Run This Flow – Select the Flow (Definition) you want the policy to run when the system detects the Flow Event. If you are following along with the walkthroughs in this section, select the Flow Definition you created earlier.
Name – Enter an appropriate name for the policy.
Display Name – Enter the name to be displayed for the policy in the EmpowerID UI.
Description – Enter a brief characterization of the policy.
Locale Key (Unique Name) – Optional setting used to set the locale key for the Flow Policy name
Local Key for Description – Optional setting used to set the locale key for the Flow Policy description
Is Shipping Data – For internal use
Click Save.
Close the Add New Flow Policy form.
Step 2 – Specify the Scope
Search for the policy you created and click the Name link for it.
This directs you to the View One page for the policy. View One pages are designed to facilitate the viewing and management of the corresponding objects in EmpowerID.
Click the Add [+] button in the Flow Policy Applies To accordion.
Select the Scope Type. Options include the following:
Scope Type | Description | Example |
|---|---|---|
Parent Assignee | Scopes the policy to all objects belonging to the selected parent. Assignee options include:
| Partner in Partners Business Role and Location HDQ Sales group All Access Management Role … |
By Location | Scopes the policy to all objects in or below a specified location. | Dublin |
Query-Based Collection | Scopes the policy to all objects belonging to the query-based collection; for example, if you want certain flow items to occur when a user is added to a specific employee subset, you could set the scope to a Query-Based Collection containing the subset. | Newly Onboarded Help Desk Personnel in Athens Hired within the last 5 days The Query-Based Collection must already exist to use it. For more information about Query-Based Collections and their use, see About Query-Based Collections |
Specific Resource | Scopes the policy to a specific resource belonging to a given resource type. This is useful in situations where an organization may want specific flow items to occur in a specific order, for example, when an executive leaves or moves. | Resource Type: Person Resource: Bob Smith |
Enter a whole number from 1 to 100 in the Priority (Lower is Higher Priority) field. This is used to specify which policy takes precedence in the event an object to which the Flow policy applies falls within the scope of another Flow policy.
Leave Is Shipping Data deselected; the field is for internal EmpowerID use.
Click Save to add the scope to the policy. In the below screenshot, a Query-Based Collection is added as the scope type.
If you have completed all the steps in the walkthroughs for this section, you have successfully set up a simple automated process for handling contractor departures. The No Code Flow will now automatically execute the specified offboarding process whenever a "Person Leaver" event is triggered for contractors.