Key concepts
Before we dive into the components that make up the FlowX.AI Platform, let's go through the keywords and concepts you'll read about in the docs.
🧩

Process

Let's start with the basics: the core building block of the platform is a process. Think of it as a representation of your business use case, for example making a request for a new credit card, placing an online food order, registering your new car or creating an online fundraiser supporting your cause.
A process is nothing more but a series steps that need to be followed in order to get to the desired outcome: getting the new credit card, gathering online donations from friends or having your lunch brought to you. These steps involve a series of actions, whether automated or handled by a human, that allow you to complete your chosen business objective.
To easily design and model process flows, we use the standard BPMN 2.0 graphical representation. In case you are not familiar with the standard, the next section covers some basic concepts:
Some of the process steps might require making business checks or validations. Business rules and decisions can be defined on nodes using either the DMN standard or the MVEL expression language. You can use the one you are most comfortable with.
In order to achieve real-time data feeds between the FlowX.AI platform components, and make sure they integrate seamlessly, we have chosen an event-driven architecture.

Process Instance

Once the desired processes are defined in the platform, they are ready to be used. Each time a process needs to be used, for example each time a customer wants to request a new credit card, a new instance of the specified process definition is started in the platform. Think of the process definition as a blueprint for a house, and of the process instance as each house of that type that is being built.
From this point on, the platform takes care of following the process flow, handling the necessary actions, storing and interpreting the resulting data.

Token

Token is the concept that describes the current position in the process flow. When you start the process you have a graph of nodes and based on the configuration you will go from one to another based on the defined sequence (connection between nodes).

Data Model

In FlowX we don't use a strict data model, we build it from node to node as it suits the business flow. When we need to integrate with an external system we need to map the data model available in the node that sends the data to an integration with the data model expected by the integration.
Last modified 7mo ago