FlowX.AI architecture
Let’s delve into the core components that power the FlowX.AI platform, providing a comprehensive understanding of its capabilities and functionalities.
FlowX Designer
The FlowX 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.
The platform has no-code/full-code capabilities, meaning applications can be developed in a visual way, available for anyone with a powerful business idea. So we’re talking about business analysts, product managers - people without advanced programming skills, and also experienced developers.
The process visual designer works on BPMN 2.0 standard - meaning that the learning curve for business analysts or product managers is quite fast. Thus, creating new applications (e.g. onboarding an SME client for banks) or adding new functionality (allow personal data changes in an app) takes only 10 days, instead of 6 to 8 months.
Explore more:
FlowX Designer
Microservices
FlowX.AI leverages a suite of microservices to drive its functionality:
FlowX 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.
You can use FlowX Engine to do the following:
- 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 DB as FlowX Admin)
FlowX Engine runs the business processes, coordinating integrations and the omnichannel UI. It is a Kafka-based event-driven platform, that is able to orchestrate, generate and integrate with any type of legacy system, without expensive or risky upgrades.
This is extremely important because often, digital apps used by a bank’s clients, for example, are limited by the load imposed by the core banking system. And the customers see blocked screens and endlessly spinning flywheels. FlowX.AI buffers this load, offering a 0.2s response time, thus the customer never has to wait for data to load.
FlowX Engine
FlowX SDKs
SDKs are used in the Web (Angular), and Android applications to render the process screens and orchestrate the custom components.
Explore more:
FlowX SDKs
FlowX 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 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.
Scheduler microservice communicates with the FlowX Engine through Kafka Event Queue ⇾ it creates a new message (write some data) then will send that message to Kafka (with the scheduler address) → when the reminder time comes up, the scheduler will put back a new message in the Kafka layer with engine’s destination (time + ID of the process).
Scheduler
FlowX 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.
License Manager
FlowX Admin
Used for storing and editing process definitions, FlowX Admin connects to the same database as the FlowX Engine, ensuring consistency in data management.
Admin setup
FlowX 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:
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.
Integrations
In summary, FlowX.AI offers a robust and versatile architecture that empowers users to create, manage, and integrate applications seamlessly, without the need for extensive coding expertise. Its microservices, SDKs, and plugins work in harmony to drive efficiency and innovation in application development and business process management.
Was this page helpful?