Managing flow designer

Edit online

IBM® Verify Flow designer facilitates in creating, managing, and implementing a customized requirement by using a set of pre-defined tasks. These tasks can be used individually or with other tasks to create the appropriate flow. A custom requirement can be a user onboarding scenario that prompts a user with specific messages or instructions to achieve a specific function.

Before you begin

Note: This feature can be enabled upon request. To request this feature, contact your IBM Sales representative or IBM contact and indicate your interest in enabling this capability. If you have permission to create a support ticket, create a support ticket with the feature name "flow designer". Note that IBM Verify trial subscriptions cannot create support tickets.
  • You must have administrative permission to complete this task. Additionally, a user with readFlows permission can view and run the flow or with manageFlows permission can have complete access to the Flow designer. For more information on creating user role, see Creating an administrator role.
  • Log in to the IBM Verify administration console as an Administrator. For more information, see Accessing IBM Verify.

Procedure

  1. Log in as an administrator on Verify. Navigate to the profile icon and click Switch to admin.
  2. Select User experience > Flow designer.
    Note: IBM Verify trial subscriptions can create maximum of 10 flows in flow designer. To alter the limit on the number of flows, contact your IBM Sales representative or IBM contact.
  3. If no previous flows exist in the tenant, click the Create flow to design a new flow. See Creating a flow for further details. Alternatively, click the Import hyperlink to upload existing flow file from the local system
    • Import feature supports .json and .bpmn (deprecated) files up to 5 MB.
    • Currently, the system converts the .bpmn file to .json before importing. It is recommended to use .json from now onwards.
      Note: If flows exist in the tenant, you can Export a record, update the required details in the exported .json file, and then Import the modified file to proceed.
    • It may be needed to make environment-specific configuration changes within the flow and its tasks after the file is imported.
  4. For existing flows, the Flow designer screen displays the records in a tabular format, providing Description, Last modified and Status details. The screen provides search, import, refresh, and pagination options. Hover-over the flow record and click the menu icon to select from the Export, and Delete options.
    • The Export option enables exporting the .json flow file. The file name can be modified and entered in the File name field, if needed.
      Note:
      • The functionality supports exporting the core flow .json file and not the dependencies such as forms, or pages.
      • It is not required to enter the .json extension in the File name field.
    • The View trace logs option is only displayed for the Published flow. See Managing Trace view for further details.
    • The Preview option is only displayed for the Published flow. Clicking the option opens the flow in a read-only mode along with a defined toolbar that enables to do certain actions.
      Note: The Published flow cannot be edited in Preview mode.