Edit flows
This section provides instructions on how to edit and configure existing IO flows.
Edit a flow
-
Open the left sidebar and select Visual Identity Orchestrator.
This displays a list of flow categories.
-
Select the desired category type from the menu.
-
On the right side of the flow, under column actions, select the pencil icon to edit the flow.
A dialog box opens with the General Configuration.
You can also edit a flow directly within the IO designer during the design phase.
-
Edit the Name and Description, and select if the flow is Active or Inactive (if you don't want it to be used yet).
On some flow types, you can also choose if it is a default flow for the specific flow type.
This option is available on flow subtypes that manage user onboarding and authentication:
-
Invite user
-
Registration
-
Delete user
-
Update Password
-
Reset Password
-
Oauth Consent
-
Lock user
-
Unlock user
-
Login and Logout
-
Optional configuration functions
The following optional functions are available:
Tags
You can assign tags to the flow. Tags help you more easily filter, organize, and quickly find your flows. You can freely type custom tags and press Enter to create them, or you can select from a list of predefined tags.
Enable nodes tracking
When enabled, the system tracks and records the execution of nodes within the flow into the database. This provides detailed visibility into the flow's behavior, allowing for auditing, debugging, and monitoring of every step in the process.
Available options:
-
Always: Each step executed within the node-based flow is logged, providing full traceability of the flow's execution.
-
If there is at least one error: Every step of the flow is logged only if at least one error occurs during execution. This allows you to capture detailed diagnostic information when something goes wrong, without producing unnecessary logs for successful runs.
-
In case of flow failure: The system logs the executed steps only when it encounters a flow failure. This provides a concise record of what happened leading up to the failure, helping with troubleshooting while keeping logging minimal during normal operation.
Next steps
Continue to design and modify your flow.
