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 Items

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

« Previous Version 2 Next »

After creating a Flow Definition that represents the business process you want to automate with a No Code Flow, the next step is to create Flow Items for each action you want to occur within that flow. Using off-boarding as an example, actions could include disabling accounts, removing individuals from organizational groups, archiving emails, revoking access to company resources, and terminating their EmpowerID Person object within a specified timeframe. In this article, we will create a Flow Item that disables a user’s EmpowerID Person account and add the Flow Item to the Flow Definition created earlier.

Procedure

Step 1 – Create a Flow Item

  1. Navigate to the Find Business Request Flow page by expanding Low Code/No Code Workflow and clicking No Code Flows.

  2. Select the Flow Items (Activities) tab and click the New Flow Item button.

     

  3. Enter the details for the Flow Item:

    • Item Type Action – Select the Item Type Action that represents what will occur when the Flow Item executes. In this example, we want to disable the EmpowerID Person account for all people leaving the organization, so we will select “PersonDisable.”

    • Scope Type (How to Get Items) –Select the scope type (resource type) for the Flow Item. In this example, since we want to disable the EmpowerID Person account for all people leaving the organization, we will select “Person Resource” as the scope type.

    • Item Collection Filter – Optional setting

    • Threshold Item Count – This setting specifies the maximum number of items the system can process using the default policies associated with the Flow Item. If the number is greater, the system will process Flow Item objects in accordance with the policy specified in the Over Threshold Switch to Item setting.

    • Over Threshold Switch to Item – Specifies the policy the system is to use to process Flow Item objects if the number of items surpasses the number specified in the Threshold Item Count setting.

    • Name – Name for the Flow Item, such as “Person Disable.”

    • Display Name – Name of the Flow Item in the EmpowerID UI.

    • Description – Description of the Flow Item

    • Fulfillment WF JSON – This allows you to add JSON to the fulfillment workflow

    • Is Shipping Data – Internally used

  4. Save the Flow Item.

  5. Repeat the above steps to create any other Flow Items needed.

Step 2 – Add Your Flow Items to the Flow Definition

  1. Select the Flow Definitions tab on the Find Business Request Flow page and search for the Flow Definition you created earlier.

  2. Click the Name link for the definition.


    This directs your browser to the View One page for the Flow Definition. View One pages are designed to facilitate the viewing and management of their corresponding objects in EmpowerID.

  3. Click the Add New button in the Flow Items and Sequence accordion.

  4. Enter the following information in the dialog to add the Flow Item created above to the definition:

    • Run This Flow Item – Select the Flow Item created above

    • Start After X Hours – Specify the number of hours the system should take after detecting the Flow Event trigger before executing the Flow Item.

    • Depends on Item – If the Flow Definition contains a Flow Item that needs to be executed before this item, specify it here.

    • Override Approval Policy (Optional) – This optional setting allows you to select a different Approval Policy other than the one specified for the Item Type Action set on the Flow Item. For example, if the Item Type Action is “PersonDisable” and the Approval Policy for the action requires three approvals before the system fulfills it, you can override this and select an Approval Policy that requires fewer or no approvals.

    • Fulfillment WF JSON – This optional setting allows you to add JSON for custom configuration.

  5. Click Save.

  6. Repeat the above steps to add other Flow Items to the definition as needed. Keep in mind that when adding multiple items to a definition the system will process the items in the order in which you the items have been added.

Now that you have created the Flow Items and added them to the definition, the last step is to create the appropriate Flow Policy for your No Code Flow.

  • No labels