
FlowX.AI Designer
The FlowX.AI Designer is a collaborative, no-code, web-based application development environment, designed to facilitate the creation of web and mobile applications without the need for coding expertise. It offers a wide range of capabilities:- Develop processes based on BPMN 2.0 standards.
- Configure user interfaces for processes, both generated and custom.
- Define business rules and validations via DMN files or via the MVEL, or other supported scripting languages.
- Create integration connectors in a visual manner.
- Design data models for your applications.
- Adding new capabilities by using plugins.
- Manage users access roles effectively.
FlowX Designer is built to administrate everything in FlowX.AI. It is a web application that runs in the browser, meaning that it resides out of a FlowX deployment.
FlowX.AI Designer
Microservices
FlowX.AI leverages a suite of microservices to drive its functionality:- FlowX.AI Engine
- FlowX.AI SDKs
- FlowX.AI Content Management
- FlowX.AI Scheduler
- FlowX.AI License Manager
- FlowX.AI Admin
FlowX.AI Engine
We call it the engine because itβs a nice analogy, once deployed on an existing stack, FlowX.AI becomes the core of your digital operating model.
- create any type of external or internal facing application
- redesign business processes from analog, paper-based ones to fully digital and automated processes
- manage integrations, so you can hook it up to existing CRMs, ERPs, KYC, transaction data and many more
- to read process definitions (if it is connected to the same database as FlowX Admin)
FlowX.AI Engine
FlowX.AI SDKs
SDKs are used in the Web (Angular), and Android applications to render the process screens and orchestrate the custom components. Explore more:FlowX.AI SDKs
FlowX.AI Content Management
This is another Java microservice that enables you to store and manage content. The go-to place for all taxonomies. The extension offers a convenient way of managing various content pieces such as lists or content translations. Anything that is under content management is managed by the CMS backend service. To store content, the service will use a MongoDB database (unstructured database). For example, each time you edit an enumeration, the FlowX Designer will send an HTTP request to the microservice.Content Management
FlowX.AI Scheduler
If you need to set a timer on a process that needs to end after X days, you can use the FlowX Scheduler microservice. It is a service that is able to receive requests (like a reminder application) to remind you in X amount of time to do something.When you start a process, the process must have an expiry date.
FlowX.AI Scheduler
FlowX.AI License Manager
Used for displaying usage reports related to the FlowX.AI platform within the FlowX Designer, ensuring transparent monitoring and management of the platform.FlowX.AI License Manager
FlowX.AI Admin
Used for storing and editing process definitions, FlowX Admin connects to the same database as the FlowX Engine, ensuring consistency in data management.FlowX.AI Admin setup
FlowX.AI custom plugins
Plugins are bits of functionality that allow you to expand the functionality of the platform - for example, we have the following custom plugins:- FlowX.AI Notifications plugin
- FlowX.AI Documents plugin
- FlowX.AI OCR plugin
- FlowX.AI Task Management plugin

Plugins
Authorization & Session Manager
We recommend Keycloak, a component that allows you to create users and store credentials. It can be also used for authorization - defining groups, and assigning roles to users. Every communication that comes from a consumer application, goes through a public entry point (API Gateway). To communicate with this component, the consumer application tries to start a process and the public entry point will check for authentication (Keycloak will send you a token) and the entry point validates it.Keycloak Documentation
Integrations
Connecting your legacy systems or third-party apps to the FlowX Engine is easily done through custom integrations. These can be developed using your preferred tech stack, the only requirement is that they connect to Kafka. These could include legacy APIs, custom file exchange solutions, or RPA.