Skip to main content
The first step in building applications with FlowX.AI is creating a project. Projects serve as organized containers containing all the resources needed for your business solutions, including process definitions, UI components, and integrations.
Projects list in FlowX.AI Designer filtered by project name

What is a project?

A project in FlowX.AI is a structured container that groups all the resources required to implement a business solution. It’s not just a collection of processes - it’s a comprehensive unit that manages the entire lifecycle of your app.

Centralized Management

Manage all resources, processes, and dependencies in one place, reducing context-switching

Version Control

Track changes with versioning for processes, resources, and configurations

Multi-Environment Deployment

Deploy consistent builds across development, QA, and production environments

Resource Organization

Ensure clarity with structured resources and reduce configuration errors

Project lifecycle

In FlowX.AI, a project follows a well-defined lifecycle from creation to deployment:
1

Create Project

Define basic project properties and settings
2

Configure Resources

Add and configure all necessary components
3

Create Version

Capture project state at significant milestones
4

Build Package

Create immutable deployment package from a version
5

Deploy

Release to development, QA, or production environments
This page covers creating and configuring a project, then outlines versioning, builds and deployment.

Creating a project

1

Access the Projects Section

Log in to FlowX.AI Designer and navigate to the Projects section from the main navigation.
You need permission to create projects in the workspace. If the + button is missing on the Projects page, contact your workspace administrator.
2

Initiate Project Creation

Click the + button next to the search field to open the Create Project dialog.
Create Project dialog with the name, platform and access management fields
3

Define Project Properties

Configure the basic properties for your project:
  • Name (required): Enter a name that clearly identifies your business solution. Use only letters, numbers and underscores, without spaces (for example loan_origination).
  • Platform: Select the platform you want to use for your project:
    • Omnichannel (selected by default)
    • Web Only
    • Mobile Only
  • Access Management: Optionally, add users or groups and choose their role on the project.
Click Create to create the project.
4

Adjust version settings (optional)

The creation dialog doesn’t ask for these settings. A new project starts with FlowXTheme, English as the default language, the en-US locale, the Short date format, 1 to 2 decimals and the ISO Code currency format. To change them, open Version Settings in the project navigation:
  • Project Theme (General tab): Choose a theme to apply a consistent look and feel
  • Runtime Display Formatting (Formatting tab):
    • Minimum Decimals and Maximum Decimals: Configure how numbers are displayed
    • Date Format: Short, Medium, Long, Full or Custom
    • Currency Format: Set display as ISO code (USD) or symbol ($)
  • Languages (Languages tab):
    • Set a default language (e.g., English)
    • Add additional languages for localization support
Project language settings serve two important purposes:
  • They fill the default state for preview in the UI Designer
  • They enable you to create translatable values in enumerations and substitution tags
Version Settings page, General tab, with platform, project entry point and project theme

Configuring project resources

After creating your project, you’ll need to configure various resources before you can build and deploy your app. These resources form the foundation of your solution.
1

Configure Project Resources

Your project includes these key resource sections:

Processes

Define business processes and subprocesses that orchestrate your application workflows

Project Data Model

Define the data structure shared by the processes in your project

Reusable Resources

Build UI templates, custom components, and functions you can reuse across processes

UI Flows

Design screen flows and interfaces with the visual UI builder

CMS

Configure enumerations, substitution tags, media, notification templates, and document templates

Task Manager

Set up views, stages, and allocation rules for workload management

Integrations

Connect to external systems through data sources, workflows, and proxy connections

Dependencies

Add libraries containing reusable resources shared across projects

Configuration Parameters

Define environment-specific parameters for deployment flexibility

Version Settings

Manage platform type, themes, formatting, and languages for the project version
Resource Inventory: Your project can include the following components:Process Resources:
  • Process definitions with BPMN diagrams
  • Action configurations and task settings
  • Subprocess definitions and connections
UI Resources:
  • Screen layouts and component configurations
  • Form definitions and validation rules
  • Navigation flows and interaction patterns
Content Resources:
  • Enumerations for dropdown menus and selections
  • Substitution tags for dynamic content
  • Media assets (images, videos, documents)
Integration Resources:
  • API endpoint configurations
  • Data mappings and transformations
  • Workflow definitions for system interactions
Supporting Resources:
  • The project theme (themes themselves are managed in Design Assets → Themes)
  • Configuration parameters for environments
  • Library dependencies for shared functionality
Configuration Best Practices:
  • Begin with process definitions before configuring supporting resources
  • Use clear, consistent naming conventions across all resources
  • Configure reusable components in libraries when they’ll be used in multiple projects
  • Test individual components before integrating them into the complete workflow
  • Set up environment variables for settings that differ between environments
  • Create versions after completing significant resource configurations
2

Create Process Definitions

Process definitions are the core of your application, defining the user journey and business logic:
  • Navigate to the Processes section
  • Click the + button to open the Create process dialog
  • Use the BPMN editor to design your process flow
  • Configure actions, forms, and integration points

Learn more about Process Definitions

3

Design User Interfaces

Create the screens and components users will interact with:
  • Open the UI Designer from a User Task node in your process, or design screen flows in the UI Flows section
  • Create screens for each user-facing step in your processes
  • Configure forms, buttons, and other interactive elements
  • Design responsive layouts for different device types
4

Configure Integrations

Set up connections to external systems and services in the Integrations section:
  • Define data sources for the systems you connect to (REST APIs, databases, email, and more)
  • Configure authentication and security settings
  • Create workflows that orchestrate calls to external systems
  • Test connections to ensure proper data exchange
5

Set Configuration Parameters

Define environment-specific variables:
  • Add parameters that will differ between environments
  • Set a value, then override it per environment in Configure Params Overrides on the project’s Runtime tab
  • Mask sensitive information like passwords and API keys
Configuration Parameters page listing four parameters with their value and type

Project lifecycle management

After configuring your project resources, you’ll need to prepare it for deployment through versioning and building:
1

Create Project Version

When your project configuration reaches a milestone:
  • Create a version to capture the current state
  • You can create multiple versions and commit them before creating a build
  • Versions can be modified until they are committed
  • Committed versions are locked and cannot be changed
2

Create Build

To deploy your project to an environment:
  • Create a build from any committed version
  • Builds are immutable and serve as deployable packages
  • Each build contains exactly one version of a project
  • Once a build is created, its contents (processes, enumerations, substitution tags, integrations) cannot be edited - you’ll need to create a new project version for changes
    Builds list on the Runtime tab showing two builds created from committed versions
3

Deploy Build

Move your build to the target environment (for example development for testing, QA for validation, production for end users):
  • Export the build with Export Build and import it in the target environment
  • In the target environment, use Runtime Settings → Active Policy to choose which build runs
Configuration parameters set for specific environments will be applied during deployment.

Best practices

Projects contain all your process definitions and resources. Use clear naming conventions and proper documentation to maintain organization as your project grows.
  • Project Naming: Use clear, descriptive names that reflect business purpose
  • Project Scope: Keep projects focused on specific business domains
  • Documentation: Add comprehensive descriptions to your project and components
  • Version Control: Make effective use of the built-in versioning capabilities
  • Configuration Management: Use environment variables for deployment-specific settings
  • Dependency Management: Carefully manage library dependencies to avoid conflicts
  • Testing: Validate changes in development before promoting to production

Next steps

After creating your project, you can proceed to:

Create Process Definition

Define your first business process within the project

Frequently asked questions

Open the project’s version menu, select Start New Version, and make your changes. When you are done, select Commit Changes to lock the version.
Creating a build captures a snapshot of the project version, consolidating resources into a single deployable package. Builds are immutable and cannot be edited once created.
Yes. Add languages in the Languages tab of Version Settings, and set the default locale and display formats (dates, numbers, currencies) in the Formatting tab. These settings apply to the project version, not to individual environments.

Learn more about Localization

A Project Version is a snapshot of resources and configurations. A draft version can be modified until you commit it; committed versions are locked. A Build is a deployable package created from a committed version, and it is immutable once deployed.
Open Dependencies in the project navigation and select the desired library. Choose the build you want to use, and its resources will be accessible within your project.
No, a build is immutable. To make changes, modify the project version, create a new version, and deploy a new build.
Use a controlled environment like Dev or UAT to test new builds of the library before updating the dependency in your main project. This allows you to validate changes and ensure they don’t negatively impact your project.
When a dependency is updated to a newer build, any resources that were modified in the library will reflect the latest version. Projects have control over when to update, so older versions remain stable until the dependency is manually updated.
Last modified on November 12, 2026