Flow

Question 1

What is flow?

Answer 1

Flow accelerates and optimizes the development of Digital Sales customer flows in a digital banking context. It is a modern, user-focused workflow solution that is fully integrated into the Backbase Platform.

Question 2

Flow consists of:
provides
designed

goal

Answer 2

Flow Platform

The Flow Platform provides the customer interaction, process automation and case data persistence capabilities that underly every flow. The Flow Platform is designed to help software developers easily and efficiently create account origination and onboarding flows.

Reference flows

A customer flow is a set of interactions, business processes, integrations, that work together out of the box to accomplish a particular business goal, such as enabling a customer to open an account or apply for a loan. Flow provides a set of reference flows that serve as examples of how to implement different flows.

Question 3

What are the components that make up flow

Answer 3

Customer experience
Customers interact with custom interaction widgets in the customer experience

Case Manager experience
An employee experience that is exposed that is the main entry-point to all flows. Employees will have access to processes and case data to manage cases through this experience.

Custom flow
The back-end service of Flow that lives behind the Edge Service. Developers create the custom flow using a Spring starter project.

Question 4

What are the pieces that make up the customer experience

Answer 4

Customer experience

Customers interact with custom interaction widgets in the customer experience. These widgets are built on top of widget architecture 3.

Question 5

What are the pieces that make up the case manager experience

Answer 5

Case Manager experience

Backbase has developed an employee experience that is exposed via Experience Manager. This experience is the main entry-point to all flows. Employees will have access to processes and case data and can perform user tasks on all user flows.

Case Manager widgets

Out-of-the-box widgets available to employees in the Case Manager experience. Typical widgets include views on specific case data and forms to complete particular employee user tasks.

Custom task widgets

Developers create these widgets for employees to perform tasks specific to a certain customer flow.

Question 6

What are the pieces that make up the case custom flow experience

Answer 6

Custom flow

The back-end service of Flow that lives behind the Edge Service. Developers create the custom flow using a Spring starter project, see Extend and build.

The custom flow incorporates the following modules. Each module exposes a REST API that is specified using OpenAPI.

interaction-engine

A Spring Boot Starter module that provides a framework for building interactions and managing interaction states. This module exposes an API, specified in the flow-interaction-restapi-spec, that custom interaction widgets communicate with. It uses a database table to persist the progress through the form.

process-engine

The Spring Boot Starter module that adds Business Process Model and Notation and Domain Model and Notation functionality. It is based on Camunda and exposes an API, specified in the flow-process-restapi-spec, that Case Manager widgets and custom task widgets communicate with. It requires a database.

case-data-store

The Spring Boot Starter module that adds case data management to the platform. It is the central component in Flow that is referenced from all other components. It is optional, but without this component you lose many default features. The case-data-store exposes an API, specified in the flow-casedata-restapi-spec, that Case Manager widgets communicate with for CRUD operations to the case. This engine uses a database table to persist the case data.