> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flowx.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# FlowX.AI 5.4.0 Release Notes

> SaaS multi-tenant platform capabilities, database tenant isolation, email-triggered processes, MCP server enhancements, and backend performance improvements.

<Info>
  FlowX.AI 5.4.0 introduces foundational support for a multi-tenant platform, enabling organization management and improved tenant isolation in the SaaS deployment model.
</Info>

<Note>
  **Deployment models** - Starting with v5.4.0, FlowX.AI is available in two deployment models:

  * **Self-Managed** (On-Premises / Customer Cloud)
  * **FlowX SaaS** (FlowX-hosted)

  **Feature availability badges:**

  * <Badge color="blue" icon="cloud">SaaS</Badge> Features exclusive to FlowX SaaS deployments
  * <Badge color="red" icon="building">Self-Managed</Badge> Features specific to self-managed deployments
  * <Badge color="green" icon="globe">All Deployments</Badge> Features available in both deployment models
</Note>

**What's new?**

<Tabs>
  <Tab title="SaaS & multi-tenancy">
    <Info>
      The features described in this section apply to **FlowX SaaS deployments**.\
      Self-managed deployments are not affected unless explicitly stated.
    </Info>

    FlowX.AI 5.4.0 introduces initial SaaS capabilities enabling multi-tenant deployments with organization management and tenant isolation.

    🏢 [**SaaS Multi-Tenancy**](#saas-multi-tenancy) - Multi-tenant platform with organization isolation and provisioning

    ### **SaaS multi-tenancy**

    <Card title="SaaS multi-tenancy" icon="building" iconType="duotone">
      Multi-tenant SaaS capabilities enable multiple organizations to operate independently on shared infrastructure. Each organization receives dedicated resources while maintaining complete isolation from other tenants.

      <CardGroup cols={2}>
        <Card title="Multi-tenant architecture" icon="building">
          Multiple organizations operate on shared infrastructure with complete isolation
        </Card>

        <Card title="Tenant isolation" icon="shield-check">
          Complete data and authentication isolation between organizations
        </Card>

        <Card title="Organization provisioning" icon="server">
          Automatic provisioning of dedicated resources for each organization
        </Card>

        <Card title="Resource management" icon="folder-tree">
          Each organization receives dedicated resources and project spaces
        </Card>
      </CardGroup>

      <Card title="Documentation" icon="book" href="/5.9/docs/saas/saas-overview">
        See the complete FlowX SaaS documentation for guides and best practices.
      </Card>

      <Badge color="purple" icon="star">Major Feature</Badge>
      <Badge color="blue" icon="cloud">SaaS</Badge>
    </Card>

    ***
  </Tab>

  <Tab title="AI & Integration">
    Enhanced MCP server management.

    📧 [**Email Trigger**](#email-trigger) - Start processes from external email events with configurable validation rules\
    💬 [**Chat Component**](#chat-component) - Standalone chat tab for AI-powered conversational interfaces\
    🔧 [**MCP Server Improvements**](#mcp-server-improvements) - Enhanced audit logging, resource management, and tool updates

    ### **Email trigger**

    <Card title="Email trigger" icon="envelope-open-text" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          FlowX.AI 5.4.0 introduces Email Trigger as a new Data Source type in Integration Designer, enabling processes to be started automatically when emails are received. Connect to IMAP mail servers, monitor specific mailboxes, and create process instances with the email data.

          <Info>
            Email Triggers bridge external communication channels with FlowX.AI process automation, enabling organizations to automatically route and process incoming emails through defined business workflows.
          </Info>

          <Card title="Documentation" icon="book" href="/5.9/docs/platform-deep-dive/integrations/email-trigger">
            See the complete Email Trigger documentation for configuration guides and examples.
          </Card>
        </Tab>

        <Tab title="Key Features">
          <CardGroup cols={2}>
            <Card title="IMAP Connection" icon="envelope">
              Connect to any IMAP-compatible email server with SSL/TLS support
            </Card>

            <Card title="Message Start Event" icon="play">
              New trigger type option in Message Start Event nodes to use Email Triggers
            </Card>

            <Card title="Attachment handling" icon="paperclip">
              Automatic upload of email attachments to Document Plugin with file validation
            </Card>

            <Card title="Validation rules" icon="filter">
              Configure allowed file types, maximum file size, and attachment count limits
            </Card>

            <Card title="Manage triggers" icon="list-check">
              Central Runtime page to activate, deactivate, and monitor email triggers
            </Card>

            <Card title="Failed triggers" icon="triangle-exclamation">
              Dedicated page to view and troubleshoot failed email processing attempts
            </Card>
          </CardGroup>
        </Tab>

        <Tab title="Configuration">
          **Data Source Settings:**

          | Field       | Description                       |
          | ----------- | --------------------------------- |
          | Protocol    | IMAP (currently supported)        |
          | Server Host | IMAP server hostname              |
          | Port        | Connection port (993 for SSL/TLS) |
          | Username    | Email account username            |
          | Password    | Email account password            |
          | SSL/TLS     | Enable secure connection          |

          **Filtering Criteria:**

          * **Email Address**: Monitored email address (read-only, based on authentication)
          * **Mailbox Folder**: Folder to monitor (default: Inbox)

          **Validation Options:**

          * **Allowed File Types**: PDF, DOCUMENT, IMAGE, EXCEL, ZIP
          * **Maximum File Size**: Up to 25 MB per attachment
          * **Maximum File Count**: Limit attachments per email

          <Tip>
            All fields accept configuration parameters using `${configParam}` syntax for environment-specific values.
          </Tip>
        </Tab>

        <Tab title="Email Data Schema">
          When an email triggers a process, the following data structure is available:

          ```json theme={"system"}
          {
            "emailMessage": {
              "subject": "Support Request #12345",
              "dateTime": "2026-01-15T10:30:00Z",
              "sender": "customer@example.com",
              "body": "Email body content...",
              "fileAttachments": [{
                "filePath": "email-attachments/proc-123/file.pdf",
                "downloadPath": "/api/internal/files/uuid/download"
              }],
              "headerParams": {
                "Message-ID": "<abc123@example.com>"
              }
            }
          }
          ```
        </Tab>

        <Tab title="Use Cases">
          <CardGroup cols={2}>
            <Card title="Customer support automation" icon="headset">
              Automatically create support tickets from incoming customer emails
            </Card>

            <Card title="Document processing" icon="file-lines">
              Process attached documents through automated workflows
            </Card>

            <Card title="Request handling" icon="inbox">
              Route requests to appropriate departments based on email content
            </Card>

            <Card title="Notification processing" icon="bell">
              Process automated notifications from external systems
            </Card>
          </CardGroup>
        </Tab>
      </Tabs>

      <Badge color="purple" icon="star">Major Feature</Badge>
      <Badge color="green" icon="globe">All Deployments</Badge>
    </Card>

    ***

    ### **Chat component**

    <Card title="Chat component" icon="comments" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          FlowX.AI 5.4.0 introduces a standalone Chat tab in web container applications, enabling AI-powered conversational interfaces within your applications. The Chat component provides a dedicated space for users to interact with AI agents through a familiar messaging interface.

          <Info>
            The Chat component integrates with FlowX.AI's AI platform to enable intelligent conversational experiences powered by your configured AI agents.
          </Info>

          <Card title="Documentation" icon="book" href="/5.9/ai-platform/chat-component">
            See the complete Chat Component documentation for configuration guides and best practices.
          </Card>
        </Tab>

        <Tab title="Key Features">
          <CardGroup cols={2}>
            <Card title="Standalone chat tab" icon="message">
              Dedicated chat interface available as a standalone tab in web container apps
            </Card>

            <Card title="Message history" icon="clock-rotate-left">
              Persistent chat history with automatic scrolling to the latest messages
            </Card>

            <Card title="AI agent integration" icon="robot">
              Connect to workflows powered by AI agents
            </Card>

            <Card title="Session management" icon="id-badge">
              Automatic session handling with persistence across page refreshes
            </Card>

            <Card title="Customizable UI" icon="palette">
              Themeable components with comprehensive style configuration through Theme Admin
            </Card>
          </CardGroup>
        </Tab>

        <Tab title="Configuration">
          **Component setup:**

          * Add Chat component from UI Designer to your UI Flow
          * Select a workflow to handle chat interactions
          * Configure header, messages, and input properties
          * Apply custom styling through Theme Admin

          **Display modes:**

          * Full screen (v5.4.0)
          * Additional modes planned for v5.5
        </Tab>

        <Tab title="Improvements">
          **Session handling:**

          * Chat session ID is now generated when the first message is sent (not when opening the chat)
          * Improved session tracking

          **Message display:**

          * Latest messages are automatically scrolled into view after loading chat history
          * User input formatting (JSON, multiline text) is now preserved in displayed messages

          **Platform support:**

          * Available in both Angular and React web renderers
          * Mobile support planned for v5.5
        </Tab>
      </Tabs>

      <Badge color="purple" icon="robot">AI Integration</Badge>
      <Badge color="green" icon="globe">All Deployments</Badge>
    </Card>

    ***

    ### **MCP server improvements**

    <Card title="MCP server improvements" icon="server" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          FlowX.AI 5.4.0 enhances MCP (Model Context Protocol) server integration with improved audit logging, exception handling, and resource management capabilities.
        </Tab>

        <Tab title="Key Features">
          <CardGroup cols={2}>
            <Card title="Audit logging" icon="clipboard-list">
              Complete audit trail for MCP server operations including creation, updates, and tool execution
            </Card>

            <Card title="Tool refresh" icon="rotate">
              Update MCP servers to fetch new tools without recreating the data source
            </Card>

            <Card title="Resource tracking" icon="chart-pie">
              Track MCP server usage across workflows with proper resource management
            </Card>

            <Card title="Copy support" icon="copy">
              Properly preserve MCP server selections when copying or duplicating workflows
            </Card>

            <Card title="SSE streaming" icon="stream">
              Fixed SSE event streaming to deliver events individually as they complete
            </Card>

            <Card title="Exception handling" icon="triangle-exclamation">
              Improved error handling and reporting for MCP server operations
            </Card>
          </CardGroup>
        </Tab>

        <Tab title="Bug Fixes">
          * **Tool updates**: Updating MCP servers now correctly fetches new tools
          * **Workflow copy**: MCP server selections are preserved when copying workflows
          * **Resource usages**: Fixed resource usage tracking when copying workflows to other projects
          * **SSE events**: Events are now streamed individually instead of all at once
          * **Audit entries**: Fixed missing event and subject in audit log entries
        </Tab>
      </Tabs>

      <Badge color="purple" icon="robot">AI Integration</Badge>
      <Badge color="green" icon="globe">All Deployments</Badge>
    </Card>

    ***
  </Tab>

  <Tab title="Rendering">
    UI component enhancements and navigation improvements for web applications.

    🎴 [**Card Default Collapse State**](#card-default-collapse-state) - Configure cards to load in collapsed state by default\
    🧭 [**UI Flow Breadcrumbs**](#ui-flow-breadcrumbs) - Navigation breadcrumbs ui component for UI Flows with theme configuration\
    📊 [**UI Flow Sessions**](#ui-flow-sessions) - Monitor and manage UI Flow sessions with audit logs and process tracking\
    📋 [**Tables in Collections**](#tables-in-collections) - Add support for Table UI components within Collection UI elements

    ### **Card default collapse state**

    <Card title="Card default collapse state" icon="square-caret-down" iconType="duotone">
      FlowX.AI 5.4.0 introduces a new **Default collapse state** property for Card components with accordion functionality, allowing you to configure cards that are collapsed when first loaded.

      <Tabs>
        <Tab title="Overview">
          When using Card components with the accordion feature enabled, you can now specify whether the card should be expanded or collapsed by default when the screen loads. This provides better control over the initial presentation of content and helps manage screen real estate.

          <Card title="Documentation" icon="book" href="/5.1/docs/building-blocks/ui-designer/ui-component-types/root-components/card">
            See the complete Card component documentation for configuration details.
          </Card>
        </Tab>

        <Tab title="Configuration">
          **Default collapse state options:**

          | State         | Description                                                             |
          | ------------- | ----------------------------------------------------------------------- |
          | **Expanded**  | The card content is visible when the screen loads (default behavior)    |
          | **Collapsed** | The card content is hidden when the screen loads; users click to expand |

          <Info>
            This property is only available when the **Has accordion** setting is enabled on the Card component.
          </Info>
        </Tab>

        <Tab title="Use Cases">
          <CardGroup cols={2}>
            <Card title="Progressive disclosure" icon="layer-group">
              Start with collapsed sections to reduce initial visual complexity
            </Card>

            <Card title="Optional content" icon="eye-slash">
              Hide less important information by default while keeping it accessible
            </Card>

            <Card title="Long forms" icon="rectangle-list">
              Break up lengthy forms into collapsible sections for better navigation
            </Card>

            <Card title="FAQ sections" icon="circle-question">
              Display questions collapsed with answers revealed on click
            </Card>
          </CardGroup>
        </Tab>
      </Tabs>

      <Badge color="orange" icon="sparkles">UI Enhancement</Badge>
      <Badge color="green" icon="globe">All Deployments</Badge>
    </Card>

    ***

    ### **UI Flow Breadcrumbs**

    <Card title="UI Flow Breadcrumbs" icon="route" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          Navigation breadcrumbs UI component for UI Flows provide users with clear context of their current location within the application hierarchy. Breadcrumbs display the navigation path and enable quick navigation to parent screens.

          <Info>
            Breadcrumbs enhance user experience by providing visual navigation context and allowing users to understand their position in the application structure.
          </Info>
        </Tab>

        <Tab title="Key Features">
          <CardGroup cols={2}>
            <Card title="Navigation breadcrumbs UI component" icon="route">
              Display breadcrumbs UI component for UI Flows showing the current navigation path
            </Card>

            <Card title="Admin theme configuration" icon="palette">
              Configure breadcrumb appearance and styling through Admin theme settings
            </Card>
          </CardGroup>
        </Tab>

        <Tab title="Configuration">
          **Theme Configuration:**

          * Configure breadcrumb styling through Admin theme settings
          * Customize colors, fonts, and spacing to match your application design
          * Apply consistent styling across all UI Flows
        </Tab>
      </Tabs>

      <Badge color="orange" icon="sparkles">UI Enhancement</Badge>
      <Badge color="green" icon="globe">All Deployments</Badge>
    </Card>

    ***

    ### **UI Flow Sessions**

    <Card title="UI Flow Sessions" icon="window-restore" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          FlowX.AI 5.4.0 introduces UI Flow Sessions monitoring in the Runtime view, providing comprehensive visibility into active user sessions with UI Flows. Monitor session activity, view audit logs, track associated processes, and debug UI Flow interactions in real-time.

          <Info>
            UI Flow Sessions enable administrators and developers to track user interactions, troubleshoot issues, and monitor the health of UI Flow-based applications.
          </Info>

          <Card title="Documentation" icon="book" href="/5.9/docs/projects/runtime/ui-flow-sessions">
            See the complete UI Flow Sessions documentation for detailed usage and troubleshooting guides.
          </Card>
        </Tab>

        <Tab title="Key Features">
          <CardGroup cols={2}>
            <Card title="Session monitoring" icon="eye">
              View all active and historical UI Flow sessions with status, start date, and session IDs
            </Card>

            <Card title="Audit log" icon="clipboard-list">
              Comprehensive audit trail showing all events and actions within each session
            </Card>

            <Card title="Process tracking" icon="diagram-project">
              Monitor process instances started from UI Flows with execution status and timing
            </Card>

            <Card title="Workflow debugging" icon="bug">
              View workflow execution details, node timing, and data transformations for troubleshooting
            </Card>

            <Card title="Filtering and search" icon="filter">
              Filter sessions by UI Flow definition and search by session ID for quick access
            </Card>

            <Card title="Real-time status" icon="clock">
              Track session status updates in real-time (STARTED, ACTIVE, FINISHED, FAILED)
            </Card>
          </CardGroup>
        </Tab>

        <Tab title="Use Cases">
          <CardGroup cols={2}>
            <Card title="Session monitoring" icon="chart-line">
              Monitor active sessions to understand user engagement and identify sessions needing attention
            </Card>

            <Card title="Audit and compliance" icon="shield-check">
              Track all user interactions and actions for audit purposes and compliance requirements
            </Card>

            <Card title="Debugging" icon="bug">
              Investigate issues by reviewing audit logs, process instances, and workflow executions
            </Card>

            <Card title="Performance analysis" icon="gauge">
              Analyze session duration, process start times, and workflow execution performance
            </Card>
          </CardGroup>
        </Tab>
      </Tabs>

      <Badge color="blue" icon="monitor">Runtime Management</Badge>
      <Badge color="green" icon="globe">All Deployments</Badge>
    </Card>

    ***

    ### **Tables in Collections**

    <Card title="Tables in Collections" icon="table" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          FlowX.AI 5.4.0 introduces support for Table UI components within Collection UI elements, enabling you to display structured tabular data as items within dynamic collections. This enhancement provides greater flexibility for presenting complex data structures in a consistent, organized format.

          <Info>
            You can now embed Table components inside Collection prototypes, allowing each collection item to display data in a structured table format with columns, rows, and table-specific features.
          </Info>

          <Card title="Table Documentation" icon="book" href="/5.1/docs/building-blocks/ui-designer/ui-component-types/table">
            See the complete Table component documentation for configuration details and usage examples.
          </Card>

          <Card title="Collection Documentation" icon="book" href="/5.1/docs/building-blocks/ui-designer/ui-component-types/collection/collection">
            Learn about Collection components and how to configure collection prototypes.
          </Card>
        </Tab>

        <Tab title="Key Features">
          <CardGroup cols={2}>
            <Card title="Table in collection items" icon="layer-group">
              Embed Table components within Collection prototypes to display structured data for each collection item
            </Card>

            <Card title="Structured data display" icon="table-columns">
              Present complex data structures with columns, rows, and table-specific formatting within collections
            </Card>

            <Card title="Table features" icon="sliders">
              Leverage full Table component capabilities including sorting, filtering, pagination, and row actions
            </Card>

            <Card title="Dynamic content" icon="arrows-rotate">
              Combine Collection's dynamic data handling with Table's structured presentation for flexible layouts
            </Card>
          </CardGroup>
        </Tab>

        <Tab title="Use Cases">
          <CardGroup cols={2}>
            <Card title="Product catalogs" icon="shopping-cart">
              Display product information in table format within a collection of products
            </Card>

            <Card title="Data dashboards" icon="chart-pie">
              Create dashboard views with multiple tables showing different data sets in collection items
            </Card>

            <Card title="Report listings" icon="file-lines">
              Show report summaries in table format within a collection of reports
            </Card>

            <Card title="Comparison views" icon="code-compare">
              Compare multiple entities side-by-side using tables within collection items
            </Card>
          </CardGroup>
        </Tab>
      </Tabs>

      <Badge color="orange" icon="sparkles">UI Enhancement</Badge>
      <Badge color="green" icon="globe">All Deployments</Badge>
    </Card>

    ***
  </Tab>

  <Tab title="Platform & infrastructure">
    Backend optimizations, connector improvements, and platform stability enhancements.

    🔌 [**Connector Topic Pattern**](#connector-topic-pattern) - Dedicated Kafka topic pattern for connectors\
    ⚙️ [**Kafka Configuration Alignment**](#kafka-configuration-alignment) - Unified Kafka property names across all services with backwards compatibility\
    ⚡ [**Advancing Performance**](#advancing-performance) - Fixed advancing partition issues and improved concurrency handling

    ### **Connector topic pattern**

    <Card title="Connector topic pattern" icon="plug" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          FlowX.AI 5.4.0 introduces a dedicated Kafka topic pattern variable (`KAFKA_CONNECTORS_TOPIC_PATTERN`) for connectors, allowing custom topic patterns without affecting other platform components like document-plugin, data-search, and cms-core.
        </Tab>

        <Tab title="Problem Solved">
          **Previous Limitations:**

          <CardGroup cols={2}>
            <Card title="Shared topic pattern" icon="share-nodes">
              Connectors used the same `KAFKA_TOPIC_PATTERN` as other components, limiting customization
            </Card>

            <Card title="Security concerns" icon="shield-exclamation">
              Connectors could write to all topics with the pattern `ai.flowx.engine.receive.*`
            </Card>
          </CardGroup>
        </Tab>

        <Tab title="Solution">
          **New Configuration:**

          ```yaml theme={"system"}
          # Old configuration (shared with all components)
          KAFKA_TOPIC_PATTERN: ai.flowx.engine.receive.*

          # New configuration (dedicated for connectors)
          KAFKA_CONNECTORS_TOPIC_PATTERN: ro.uniflow.*
          ```

          **Benefits:**

          * Connectors can use custom topic patterns
          * Other components continue using the standard pattern
          * Improved security through topic isolation
        </Tab>
      </Tabs>

      <Badge color="blue" icon="gear">Infrastructure</Badge>
      <Badge color="red" icon="building">Self-Managed</Badge>
    </Card>

    ***

    ### **Kafka configuration alignment**

    <Card title="Kafka configuration alignment" icon="plug" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          FlowX.AI 5.4.0 aligns Kafka configuration properties across all services (core-services and AI platform services) by introducing standardized property names while maintaining full backwards compatibility with existing configurations.
        </Tab>

        <Tab title="New Properties">
          **Standardized Kafka Properties:**

          The following new environment variables are now available across all services:

          | Environment Variable      | Description                               | Fallback Property                |
          | ------------------------- | ----------------------------------------- | -------------------------------- |
          | `KAFKA_BOOTSTRAP_SERVERS` | Comma-separated list of Kafka brokers     | `SPRING_KAFKA_BOOTSTRAP_SERVERS` |
          | `KAFKA_SECURITY_PROTOCOL` | Security protocol for Kafka communication | `SPRING_KAFKA_SECURITY_PROTOCOL` |

          <Info>
            The new properties take precedence over the legacy `SPRING_KAFKA_*` properties. If the new properties are not set, the system automatically falls back to the legacy properties, ensuring backwards compatibility.
          </Info>
        </Tab>

        <Tab title="Benefits">
          <CardGroup cols={2}>
            <Card title="Property alignment" icon="link">
              Consistent property names across core-services and AI platform services
            </Card>

            <Card title="Backwards compatible" icon="arrow-left">
              Existing configurations using `SPRING_KAFKA_*` properties continue to work without changes
            </Card>

            <Card title="Simplified configuration" icon="sliders">
              Unified configuration approach across all FlowX.AI services
            </Card>

            <Card title="Migration flexibility" icon="arrows-rotate">
              Migrate to new properties at your own pace without breaking existing deployments
            </Card>
          </CardGroup>

          <Info>
            This change was implemented in core-services and automatically applies to all services that use the shared Kafka configuration. No action is required for existing deployments, but you can optionally migrate to the new property names for consistency.
          </Info>
        </Tab>
      </Tabs>

      <Badge color="blue" icon="gear">Infrastructure</Badge>
      <Badge color="green" icon="globe">All Deployments</Badge>
    </Card>

    ***

    ### **Advancing performance**

    <Card title="Advancing performance" icon="gauge-high" iconType="duotone">
      FlowX.AI 5.4.0 includes significant fixes and improvements to the advancing mechanism, resolving issues with stalled events and improving concurrency handling.

      <Accordion title="Stalled events fix">
        Fixed issue where NEW entries in `advancing_partition` and `advancing_partition_event` tables would become stalled and never processed. This occurred when multiple events were generated for the same partition during parallel processing.
      </Accordion>

      <Accordion title="Numeric overflow fix">
        Fixed numeric overflow error when `advancing_partition_event_seq` sequence exceeded `Integer.MAX_VALUE`. Now correctly uses `getLong()` instead of `getInt()` for sequence values.
      </Accordion>

      <Accordion title="Concurrency improvements">
        * Fixed issue with multiple events to the same partition causing negative `count_queued_events`
        * Replaced trigger-based solution with SQL transactions for atomic updates
        * Improved handling of embedded subprocess completion under concurrent load
      </Accordion>

      <Accordion title="Automated test stability">
        Resolved data inconsistencies and business exceptions that were causing automated tests to fail consistently.
      </Accordion>

      <Badge color="green" icon="bolt">Performance</Badge>
      <Badge color="green" icon="globe">All Deployments</Badge>
    </Card>

    ***
  </Tab>

  <Tab title="Bug fixes & stability">
    Comprehensive bug fixes across SaaS features, Designer, and backend services.

    🎨 [**Designer Fixes**](#designer-fixes) - UI and navigation fixes for Designer\
    ⚙️ [**Backend Fixes**](#backend-fixes) - Backend stability and performance improvements

    ### **Designer fixes**

    <Card title="Designer fixes" icon="palette" iconType="duotone">
      FlowX.AI 5.4.0 resolves Designer issues to improve stability and user experience.

      ## Navigation & routing

      <Accordion title="Navigation fixes">
        * **Fixed sidebar display** - sidebar menu now shows when accessing pages via URL
        * **Fixed subprocess navigation** - resolved 403 when navigating to subprocesses
        * **Fixed back navigation** - resolved 403 when going back from UI Flows page
        * **Fixed audit log access** - resolved errors when viewing process instance audit logs
        * **Fixed version history** - "Open version in new tab" now works correctly
      </Accordion>

      <Accordion title="UI improvements">
        * **Fixed default locale display** - locale now correctly shown in Version settings
        * **Fixed substitution calls** - resolved errors when starting processes or accessing UI Flows
      </Accordion>

      <Badge color="purple" icon="palette">Designer Stability</Badge>
      <Badge color="green" icon="globe">All Deployments</Badge>
    </Card>

    ***

    ### **Backend fixes**

    <Card title="Backend fixes" icon="server" iconType="duotone">
      Backend stability and performance improvements across core services.

      ## Process engine

      <Accordion title="Advancing & concurrency">
        * **Fixed stalled advancing events** - NEW entries no longer get stuck in advancing tables
        * **Fixed numeric overflow** - resolved overflow when sequence exceeds Integer.MAX\_VALUE
        * **Fixed concurrent updates** - resolved stale data errors for embedded subprocess completion
        * **Fixed negative counter** - resolved issue with `count_queued_events` going negative
      </Accordion>

      ## AI platform

      <Accordion title="AI integration fixes">
        * **Fixed multi-agent streaming** - streaming now works correctly for multi-agent chat
        * **Fixed SSE event delivery** - events are delivered individually as they complete
      </Accordion>

      ## Integration Designer

      <Accordion title="Workflow & data model">
        * **Fixed file upload multipart** - only file name is sent in multipart body, not full path
        * **Fixed data model duplicates** - resolved duplicate entries in mongo properties\_paths
      </Accordion>

      <Badge color="green" icon="server">Backend Stability</Badge>
      <Badge color="green" icon="globe">All Deployments</Badge>
    </Card>

    ***
  </Tab>

  <Tab title="Info">
    ## Additional information

    ### Deployment information

    <Info>
      For detailed deployment guidelines, component versions, and upgrade instructions, see the [Deployment Guidelines v5.4.0](./deployment-guidelines-v5.4).
    </Info>

    ### Compatibility

    <CardGroup cols={2}>
      <Card title="Upgrade path" icon="arrow-up-right-dots">
        Upgrade from v5.3.0 - no breaking changes for standard deployments
      </Card>

      <Card title="Component compatibility" icon="circle-check">
        Compatible with FlowX.AI SDKs (Angular/React/iOS/Android), Designer, and Database 5.4
      </Card>
    </CardGroup>

    ### SaaS features

    <Info>
      The SaaS multi-tenant features introduced in this release require additional infrastructure configuration for production deployments. Contact your FlowX.AI representative for guidance on enabling SaaS capabilities.
    </Info>
  </Tab>
</Tabs>