Building blocks
Before setting up the engine and starting process flows on it, let's go through the main related concepts.

FlowX engine building blocks

Once a process is defined and added on the platform, it can be executed, monitored and optimized. When a business process starts, we create an instance of the definition.
Think of the process instance as if the process definition is the blueprint of a house and the instance is the house.
Each process instance holds its current state and business data related to it.
The engine takes care of going through the process steps defined and handles all the business logic on the process definition.
The token is used to describe the current position in the process. The token moves from one node to the next based in the defines sequences between the nodes and the business rules defined on the exclusive gateways. In case of parallel gateways, child tokens are created for each flow branch and they are merged back into the parent token once the parallel execution part ends.
Kafka events are used for all communication between various flowx components such as the engine and the integrations and plugins. Each event type is associated with a Kafka topic to be able to keep track and orchestrate the multitude of messages sent on Kafka.
The engine is also responsible with updating the UI when some actions occur. This is done by sending messages via sockets.
Last modified 7mo ago