Skip to main content

Create Flow Definitions

Flow Definitions are blueprints that define the sequence of actions (Flow Items) required for a specific business process. When a Flow Policy triggers a Flow Definition, EmpowerID generates a Business Request containing the configured Flow Items, which then execute in the defined order. This article demonstrates creating a Flow Definition for employee offboarding.

Create a Flow Definition​

  1. Expand Low Code/No Code Workflow and click No Code Flows.

  2. Click the New Flow Definition button. New Flow Definition Button

  3. Enter the details for the Flow Definition:

    FieldDescription
    NameInternal name for the Flow Definition (e.g., "Employee Offboarding")
    Display NameName displayed in the EmpowerID UI
    Locale Key (Unique Name)Optional: Locale key for translating the Flow Definition name into other languages. Leave blank if not using multi-language support.
    DescriptionDescription of the Flow Definition's purpose and the business process it automates
    Locale Key For DescriptionOptional: Locale key for translating the description. Leave blank if not using multi-language support.
    BR Generation Stored ProcedureStored procedure that converts the Flow Definition into a Business Request. Use the default value: BusinessRequest_GenerateBusinessRequestFlowDefinitionRequest
    Business Request TypeThe type of Business Request this Flow Definition generates (e.g., "Person Leaver" for offboarding). This determines how the request appears in Business Request queues and reporting.

  4. Click Save. The new Flow Definition appears in the Flow Definitions tab of the Find Business Request Flow page. Flow Definitions List

Next Steps​

After creating the Flow Definition, create Flow Items that define the individual actions (disable accounts, remove access, send notifications) to execute as part of this Flow Definition. Once created, add these Flow Items to the Flow Definition and configure their sequence and timing. Finally, create Flow Policies to define when this Flow Definition should trigger based on specific events. The Flow Definition remains inactive until a Flow Policy references it.

Related Articles: