Back-Office Flows

Back Office Flows allow you to enhance App Data Forms with dedicated Digital Journeys that users can trigger from the form on demand. Back-office flows run within the data context of the app data form that initiated them. Once the flow is completed, users are returned to the form at the point where they left off.

For example, an online banking application based on an app data form might include steps for managing personal information, current accounts, cards, payments, etc. Additionally, a customer may wish to check their credit score. A dedicated digital journey can be attached to the app data form, where the customer consents to personal data processing, provides required details, and queries the Credit Bureau for their credit score. Once the journey is complete, the customer is returned to the banking application.

Create a Back-Office Flow

  1. In FintechOS Studio, go to Main Menu > Servicing > Back-Office Flows.
  2. Click +Insert.
  3. Create the desired back-office flow as you would Create a Digital Journey, with the following differences in mind:

Differences Between Back-Office Flows and Digital Journeys

When editing a back-office flow, you will notice the following differences from the digital journey editor.

  • Where appropriate, the tabs for editing the back-office flow reflect the differences in naming. The Analytics are not available for back-office flows.
    Digital Journey TabsEquivalent Back-Office Flow Tabs
    Journey DesignerBack-Office Flow Designer
    GeneralGeneral
    Digital Journey MapBack-Office Flow Map
    Digital Journey Navigation RulesBack-Office Flow Navigation Rules
    Analyticsn/a
  • In the General tab:
    • The Exposed API Journey option is renamed to Exposed API.
    • The Digital Journey Flows section is renamed to Subflows.
    • The Digital Journey States section is not available.
  • The Journey Settings only include options for the Actor.

Attach a Back-Office Flow to an App Data Form

  1. In FintechOS Studio, go to Main Menu > Servicing > App Data Forms.
  2. In the App Data Forms grid, double click the desired form.
  3. Open the Configs tab.
  4. In the Back-Office Flow section, click + Insert.
  5. Select the desired Back-Office Flow. Optionally, add a Description for reference.
    IMPORTANT!  
    Since back-office flows run within the data context of the app data form that initiated them, the app data form and the associated back-office flows must use the same source entity for their data models. If a back-office flow contains multiple subflows, only the first subflow must use the same source entity as the app data form.
  6. Click Save and reload.
  7. Optionally, you can use the Availability tab to define restrictions for who can run the back-office flow and when.
    • Provide a Name and Description for the availability rule.
    • Use the point-and-click Rule Expression designer to define boolean logic for the rule.
      IMPORTANT!  
      Users who will initiate the back-office flow require Security Roles with security items that grant them access to the BackOfficeFlowExecution entity (in addition to the flow's source entity).
    • You can set up multiple availability rules for the same back-office flow.
  8. Click Save and Close.

You can repeat the process above to attach multiple back-office flows to your app data form.

Run a Back-Office Flow from an App Data Form

  1. In FintechOS Portal, open the desired App Data Form.
  2. Make sure the form is in the Edit mode (if you are inserting a new record, click Save and Reload at least once).
  3. From the ellipsis menu (...), select Show Flows. This displays a list of back-office flows associated with the form that you are authorized to run.
  4. In the Flows tab, use the Start button to initiate a flow or the Continue button to resume an interrupted flow.
    In the History tab, you can review the previously run or currently running flows.
  5. Proceed with the back-office flow. Once the flow is finished, you will be returned to the app data form.