You are viewing an earlier version of the admin guide. For the latest version, please visit EmpowerID Admin Guide v7.211.0.0.

Skip to end of banner
Go to start of banner

Create Flow Definitions

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

To create a No Code Flow in your organization, it's important to understand the specific business process that needs to be automated. This could be anything from the process of an employee leaving (known as "off-boarding") to another organizational procedure. Defining this process is the first step. Once that's complete, you'll need to create a Flow Definition – essentially a blueprint that outlines the exact sequence of actions required for the specified scenario. In this article, we'll walk you through the process of crafting a Flow Definition step-by-step, providing you with all the tools and knowledge you need to effortlessly translate your organizational needs into an automated No Code Flow.

Procedure

After identifying the business process you want to automate, create a Flow Definition to represent the process. In this example, we create a Flow Definition for employee offboarding.

  1. Navigate to the Find Business Request Flow page by expanding the Low Code/No Code Workflow section and selecting No Code Flows from the navbar.

  2. Click the New Flow Definition button.

  3. Enter the details for the Flow Definition:

    • Name – Name of the Flow Definition, such as “Employee Offboarding.”

    • Display Name – Name of the Flow Definition that appears in the UI

    • Locale Key (Unique Name) – Optional setting used to set the locale key for the Flow Definition name

    • Description – Description of the Flow Definition

    • Locale Key For Description – Optional setting used to set the locale key for the Flow Definition description

    • BR Generation SPROC – Leave at the default value (BusinessRequest_GenerateBusinessRequestFlowDefinitionRequest)

    • Business Request Type – Select the Business Request Type for the Flow Definition, such as “Person Leaver.”

    • Is Shipping Data – Internally used

  4. Click Save.
    You should see the new Flow Definition in the Flow Definitions tab of the Find Business Request Flow page.

Now that you have created the Flow Definition for the No Code Flow, the next step is to create Flow Items (the individual actions you want to occur for the flow). Once created, you will add them to the Flow Definition.


  • No labels