Main Flow

The main flow defines how a workflow executes from start to finish, describing how users progress through screens while interacting with business logic and system capabilities. It models user touchpoints, navigation and decision logic, UI behavior, as well as synchronous or asynchronous interactions with services and integrations.

Workflow Elements

Click a + sign on the on the Main Flow canvas at the desired insertion point to add a new workflow element. This opens a pop-up window, allowing you to select the type of element you wish to add.

Screen

A screen represents the user interface displayed at a specific step in the workflow. The UI elements (headings, text, buttons/actions, tables, inputs/data attributes, widgets, etc.) define the layout of the screen.

Default Next and Back Buttons

The Default Next Button and Default Back Button are automatically included on every screen and can only be hidden, never deleted (instead of the Delete icon, they display an On/Off toggle).

Attributes

Each attribute displayed on screen is bound to a Data Domain data object. If you create a new attribute from a screen, you must specify which data entity, technical variable, or dictionary it belongs to, allowing you to automatically update the underlying data model as you design the workflow.

Tables

Tables display Data Entities that contain multiple records (that are linked to their parents via one-or-more cardinalities). For instance, your Data Domain may include a Loan Applicant entity which is referenced by a Co-Debtors entity via a one-or-more cardinality (a loan applicant can have one or more co-debtors). You can use a table to list all the loan applicant's co-debtors.

When configuring a table, you can specify a subset of the data entity attributes' to display as columns and whether you want the user to be able to populate the table records via a dedicated subflow (see Subflows).

Screen Exposed Data

Attributes displayed on a screen are automatically included in the screen's data context. To expose additional data (e.g. for back-office processing) or to manage the visibility and mandatory status of various attributes:

1. Open the screen's Settings slide-out panel.
2. Click + Manage exposed data.
3. (Optional) Select the Data Domain attributes you wish to expose in addition to the ones displayed on screen. This allows you to bring an attribute value in the screen's data context without displaying it (e.g.: to retrieve the value of a birth date attribute to calculate age). You can use the search bar and filters at the top of the screen to help browse the available attributes.
   IMPORTANT!  
   Hidden attributes remain in the screen's document object model. Do not store sensitive information in the hidden attributes.
4. Configure which attributes are mandatory or editable by toggling the asterisk and pencil controls respectively.

Decision

Decision elements apply conditional logic to select between alternative navigation paths. You can choose between two or more navigation paths depending on your navigation logic. For example, underwriting assessments often result in three possible navigation paths: "Approved," "Rejected", and "Manual Verification".

In its simplest form, a decision has an If navigation path at the top and an Else navigation path at the bottom. If the Else path is linked to another decision element, any additional paths are added as Else If paths. Otherwise, additional paths are added at the bottom. This makes them the new Else path, converting the previous Else path into an Else If path. You can reorder the navigation paths using the grab handles on the left of each path to drag it in the desired position (top for If, bottom for Else, or in-between for Else If).

Use the trash bin icon to the right side of a navigation path to delete it.

Navigation paths can either connect to existing elements on the canvas (resulting in a new Connect To element downstream) or remain unlinked for later connection.

Use clear labels for conditions and paths to improve readability.

Condition Editor

You can use the point-and-click editor to define complex conditional logic for your If and Else If navigation paths without writing any code:

1. Click the + Add Expression link under the desired If or Else If condition
2. Use the point-and-click interface to define your expression.

In its simplest form, a condition is based on a single form field evaluation (e.g.: Name is not blank). The available operators depend on the data type of the form field: generic operators such as is blank or is not blank, text specific operators such as starts with or contains, date specific operators such as years since or days until anniversary, etc.

You can also create complex boolean logic by grouping conditions hierarchically with logical operators:

• AND - All conditions are true.
• OR - At least one condition is true.
• NOT AND (NAND) - Not all conditions are true (at least one is false).
• NOT OR (NOR) - All conditions are false.

Integration

Integrations are interactions with core systems or external service providers that perform specialized functions (e.g., fraud detection, identity verification, risk assessment, or credit scoring).

To select an available integration, use the list on the left to enable or disable filters for the types of integrations you wish to browse or the search box to look for the desired integration by name.

Click + Create New to open the integration editor and configure your own custom integration.

To ensure readability, define a clear and relevant title for the integration action, such as "Check Account". Specify the inputs and outputs using data attributes to guide the implementation of the journey. For best effect, attach a logo for the integrated system.

Service

Services facilitate interactions with platform back-office systems (either pre-built or custom-designed) that implement business logic to retrieve data, execute specific calculations, update other systems, and others.

The FintechOS platform includes a variety of prebuilt services for tasks such as claims management, billing and collection, or policy administration. Additionally, you can build your own custom services.

When specifying a service, define the input and output data attributes that the workflow will send to or receive from the service.

Custom Services

In complex scenarios, where you need to coordinate and integrate multiple components (such as back-office services, core systems, external service providers, tasks, etc.) to deliver a specific business outcome, you can use the Custom Service service type.

When saved for the first time, these services open a dedicated editor where you can design a subflow for your service orchestration. Once saved, the custom service will also include a Go to service link that points to its service orchestration subflow to allow further modifications.

The subflow is encased in a single Stage, and only supports Decision, Integration, Service, Message, Document, Task, and Connect To elements.

Service orchestration subflows are displayed on the Workflow Designer canvas as a single element. To view or edit them, use the Go To Service link from the service's editor or access it via the Service Orchestration menu.

Message

Messages enable communication with users through channels such as push notifications, SMS, and email. Examples include sending one-time passwords via SMS or emailing contract documents. A set of built-in providers is available for various channels.

Define a relevant title and a meaningful sample text to ensure good clarity on the canvas.

Document

Documents represent files that the user must either provide (e.g., proof of identity, income, or ownership) or receive (e.g., terms and conditions or GDPR agreements). You can also specify whether the document requires the user's agreement and/or signature.

Assign a clear title and an appropriate label to ensure good clarity on the canvas.

Task

Tasks are back-office operations that must be completed by a different user, typically a company employee. This may involve manual underwriting of an application, initiating a follow-up action within the organization, or other similar activities.

Specify the responsible actor for the task and what the task entails.

You may need to follow this element with a Decision to direct the workflow along alternate paths based on the task outcome.

Asynchronous Tasks

Select the When Completed checkbox to fork the execution flow into concurrent branches using asynchronous tasks. These tasks trigger a Service that runs in parallel with the main flow and rejoins at a defined synchronization point, where the main flow awaits its completion before continuing.

Connect To

Navigates to another element on the canvas.

Stage

Stages enhance workflow clarity by allowing you to group subsequent elements together and assign them a descriptive name. For example, you might group a sequence of screens, decisions, and integration elements used to collect and validate a user's personal data in a "Data Collection" stage.

When zooming out on the canvas, stages provide a simplified view of the journey by collapsing the enclosed elements, displaying only the stage names and the outlines of their contents.

External Step

Allows you to navigate to an external URL.

Flow

Flows are reusable sequences of workflow steps. You can use flows to:

• Modify specific attributes at multiple points in a workflow
• Simplify workflow diagrams by grouping steps into subflows
• Reuse entire workflows within other workflows

There are two types of flows:

• Local subflow - Allows you to select or create Subflows within the current workflow. This is useful when repeating the same sequence of steps multiple times or for displaying parts of the workflow in a more compact form.
• External subflow - Allows you to select an external workflow to include within the current workflow.

Move Workflow Elements

There are two grab handles above each element that allow you to drag it to a different position along the workflow path. The first grab handle moves the individual element. The second grab handle moves all the elements from that point to the end of the Stage.

When moving Decision elements, the decision node is detached from its original location and reattached at the new position along the If navigation path. The Else and Else If branches remain connected to the decision node and are moved along with it.