FlowX.AI 5.0.0 Release Notes
Latest features, improvements, and bug fixes in our newest release
This release includes the following features in Tech Preview. We encourage you to try them out and share your feedback to help us improve them. Please note that Tech Preview features may change before final release.
What’s new? 🆕
🆕 Workspaces (Multi-Tenant Architecture)🆕 Project Data Model (PDM)
🆕 FlowX Database
🆕 Multi Select UI Component
🆕 Library-to-Library Dependencies
🆕 Data Mappers
🆕 Reusable Resources
🆕 Forms in collection
🆕 Files in Integration Designer
🆕 Rendering improvements
Workspaces (Multi-Tenant Architecture)
Workspaces
Learn more about WorkspacesPlatform Evolution
👥 What This Means for Your Role
👥 What This Means for Your Role
Major Infrastructure Changes: Workspaces introduces SpiceDB integration and new database schemas for multi-tenant architecture.
- SpiceDB Integration: New permission management system requiring deployment
- Database Migration: Schema updates for workspace support
- User Storage: Users now stored in FlowX database
- Default Workspace: Existing customers get automatic migration to default workspace
Backward Compatibility: All existing functionality preserved in default workspace
Project Data Model (PDM)
Project Data Model (PDM)
Learn more about Project Data ModelNew Feature
👥 What This Means for Your Role
👥 What This Means for Your Role
Infrastructure Impact: PDM has minimal infrastructure impact - it’s a design-time feature that improves development efficiency without affecting runtime resources.
No deployment changes required - PDM is part of the design platform, not runtime
Backward compatible - Existing processes continue to work unchanged
FlowX Database
FlowX Database
Learn more about FlowX DatabaseNew Feature
👥 What This Means for Your Role
👥 What This Means for Your Role
Infrastructure Planning Required: FlowX Database creates additional MongoDB collections and requires infrastructure planning for storage, monitoring, and backup procedures.
New microservice: NoSQL DB Runner. Check the setup guide for more details.
- Storage Planning: Monitor usage as processes adopt internal database (plan for 20-30% increase)
- Performance Monitoring: Set up alerts for FlowX Database query performance
- Backup Strategy: Include FlowX Database collections in backup procedures
- Connection Pooling: Additional connection pools for database operations
- Memory: Additional 256MB-512MB per FlowX instance for database operations
Multi Select UI Component
Multi Select UI Component
Learn more about Multi SelectNew Component
👥 What This Means for Your Role
👥 What This Means for Your Role
No Infrastructure Impact: Multi Select is a pure UI component with no backend requirements. It works with existing form handling and data storage mechanisms.
Zero deployment overhead - Component is part of the UI framework upgrade
Existing data handling - Uses standard array storage, no schema changes needed
Library-to-Library Dependencies
Library-to-Library Dependencies
Learn more about Library DependenciesMajor Enhancement
👥 What This Means for Your Role
👥 What This Means for Your Role
Full Backwards Compatibility: FlowX 5.0 maintains full backwards compatibility with existing project-to-library dependencies from FlowX 4.x. All existing dependencies will continue to work without modification.
- Existing dependencies will be automatically migrated
- New library dependency features become available immediately
- No breaking changes to existing functionality
- Enhanced validation may catch previously undetected issues
Post-Migration Required: After the lib2lib migration is executed, you must clear the cache. This is necessary because a new field is added to the build mongo document.
- Complete the lib2lib migration process
- Clear the application cache to ensure the new build document fields are properly recognized
- Verify that library-to-library dependencies are functioning correctly
- Build Export Changes: Build exports now automatically include entire dependency trees (larger packages but self-contained)
- Dependency Validation: Build process now checks for dependency conflicts (enhanced validation may catch previously undetected issues)
- Deployment Consistency: Single-version constraint prevents runtime conflicts (more predictable deployments)
Data Mappers
Data Mappers
Data Mappers enable users to visually map data transfers between components with intuitive drag-and-drop functionality while maintaining full backward compatibility with existing implementations.
Learn more about Data MappersNew Feature
👥 What This Means for Your Role
👥 What This Means for Your Role
Zero Infrastructure Impact: Data Mappers is a design-time feature that enhances the FlowX Designer interface without requiring additional infrastructure or deployment changes.
Full Backward Compatibility: All existing data transfer mechanisms (like
append to parent process or output.[outputKey]) continue to work unchanged. Teams can adopt Data Mappers at their own pace.- No new microservices - Enhancement to existing designer interface
- No runtime changes - Data mapping occurs at design time
- Existing configurations preserved - Zero impact on current implementations
- Optional adoption - Teams choose when and where to use new functionality
Reusable Resources
Reusable Resources
👥 What This Means for Your Role
👥 What This Means for Your Role
Minimal Infrastructure Impact: Reusable Resources is primarily a design-time enhancement that leverages existing FlowX infrastructure with minimal additional overhead.
- Execution Context: Functions execute within existing process engine contexts - no additional runtime infrastructure required
No New Microservices: Features are integrated into existing FlowX platform components