> ## 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.6.0 Release Notes

> Conversational AI with memory and intent routing, incoming webhooks, proxy connections, unmanaged MongoDB, UI Flow session variables, chat history, and 28 bug fixes.

<div style={{position: "relative", width: "100%", paddingBottom: "52.5%", borderRadius: "12px", overflow: "hidden"}}>
  <iframe src="https://s3.eu-west-1.amazonaws.com/docx.flowx.ai/5.6/hero-5.6.0.html" style={{position: "absolute", top: 0, left: 0, width: "100%", height: "100%", border: "none"}} />
</div>

FlowX.AI 5.6.0 brings **conversational AI** to your apps. Build multi-turn chat experiences where agents remember context, classify user intent, and navigate users to the right screen — all within a single workflow. On the integration side, **incoming webhooks** let external systems start processes via HTTP, **proxy connections** route traffic through intermediary servers, and **unmanaged MongoDB** connects FlowX to your existing database infrastructure. The UI layer gains **session variables**, **route management**, **chat history**, and **suggested prompts** for richer end-user experiences.

<CardGroup cols={3}>
  <Card title="For AI builders" icon="robot" href="#conversational-workflows">
    Chat Driven workflows, session memory, intent routing, and context retrieval
  </Card>

  <Card title="For integrators" icon="plug" href="#incoming-webhooks">
    Incoming webhooks, proxy connections, unmanaged MongoDB, and base64 certificates
  </Card>

  <Card title="For UI developers" icon="palette" href="#ui-flow-session-variables">
    Session variables, route management, chat history, suggested prompts, and new UI events
  </Card>
</CardGroup>

### What changed since 5.5.0

| 5.5.0                                                | 5.6.0                                                            |
| ---------------------------------------------------- | ---------------------------------------------------------------- |
| Output Focused workflows only                        | + **Chat Driven** workflows with multi-turn memory               |
| No event-driven process starts from external systems | **Incoming webhooks** with API key auth                          |
| FlowX-managed MongoDB only                           | + **Unmanaged MongoDB** — bring your own database                |
| No conversation persistence                          | **Chat History** — browse and resume past sessions               |
| Static chat empty state                              | **Suggested Prompts** — guide users with one-click starters      |
| Certificate file paths only                          | **Base64 certificates** — paste content directly, no file mounts |
| No cross-page data in UI Flows                       | **Session variables** — persist data across pages and workflows  |

***

**What's new?**

<Tabs>
  <Tab title="AI Platform">
    Build complete conversational AI pipelines — from understanding what the user wants, to retrieving the right context, to navigating them to the right screen.

    💬 [**Conversational Workflows**](#conversational-workflows) - New Chat Driven workflow type for multi-turn conversations\
    🧠 [**Memory Capabilities**](#memory-capabilities) - Automatic session memory with summarization across turns\
    🎯 [**Intent Classification node**](#intent-classification-node) - Classify user messages and route to the right branch in one step\
    🧭 [**Navigate in UI Flow**](#navigate-in-ui-flow) - Let the AI open forms and screens with contextual data\
    🔍 [**Context Retrieval node**](#context-retrieval-node) - RAG search against Knowledge Bases without calling an LLM\
    📄 [**Extract Data from File**](#extract-data-from-file) - Three extraction methods, image support, and signature detection\
    🌐 [**Web Page Extractor**](#web-page-extractor) - Crawl web pages and extract readable content for AI processing

    See also: [Chat History](#chat-history), [Suggested Prompts](#chat-suggested-prompts), and [Markdown in chat](#markdown-in-chat-messages) in the **UI & Designer** tab.

    ### **Conversational Workflows**

    <Card title="Conversational Workflows" icon="comments" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          Chat Driven workflows are a specialized workflow type for multi-turn chat interactions. Unlike Output Focused workflows that process structured input/output, Chat Driven workflows manage ongoing dialogue — handling message exchange, session memory, and response routing through a dedicated Start node layout (Chat Session ID + User Message) and Custom Agent nodes with direct chat reply capability.

          <Frame>
            ![Conversational workflow with Custom Agent configuration](https://s3.eu-west-1.amazonaws.com/docx.flowx.ai/5.6/conversational_workflow_config.png)
          </Frame>

          <Card title="Documentation" icon="book" href="/5.9/ai-platform/conversational-workflows">
            See the complete Conversational Workflows documentation.
          </Card>
        </Tab>

        <Tab title="Key Features">
          <CardGroup cols={2}>
            <Card title="Multi-turn conversations" icon="messages">
              Support for back-and-forth conversations with persistent context
            </Card>

            <Card title="Intent routing" icon="route">
              Automatically classify user messages and route to appropriate workflow branches
            </Card>

            <Card title="Session memory" icon="brain">
              Built-in session memory with automatic summarization across conversation turns
            </Card>

            <Card title="Chat UI components" icon="message">
              Dedicated chat component with error handling and shared state management
            </Card>
          </CardGroup>
        </Tab>
      </Tabs>

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

    ***

    ### **Memory Capabilities**

    <Card title="Memory Capabilities" icon="brain" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          Conversational workflows include built-in session memory that automatically persists and retrieves conversation history. On each message, the system retrieves the last 3 turns of raw messages plus a summary of earlier exchanges, injecting them into the AI node's system prompt for context-aware responses.

          <Frame>
            ![Memory tab showing conversation summary and history](https://s3.eu-west-1.amazonaws.com/docx.flowx.ai/5.6/memory_tab_workflow_console.png)
          </Frame>

          <Card title="Documentation" icon="book" href="/5.9/ai-platform/agent-builder/memory-capabilities">
            See the complete Memory Capabilities documentation.
          </Card>
        </Tab>

        <Tab title="Key Features">
          <CardGroup cols={2}>
            <Card title="Automatic retrieval" icon="clock-rotate-left">
              Last 3 turns + summary of earlier exchanges retrieved on each message via sessionId
            </Card>

            <Card title="Smart summarization" icon="compress">
              Older conversation history is automatically summarized to fit within context limits
            </Card>

            <Card title="Per-node control" icon="toggle-on">
              Turn on memory per Custom Agent node with the **Use memory** toggle
            </Card>

            <Card title="Memory tab in console" icon="terminal">
              View retrieved memory (raw turns + summary) in the workflow console log
            </Card>
          </CardGroup>
        </Tab>
      </Tabs>

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

    ***

    ### **Intent Classification node**

    <Card title="Intent Classification Node" icon="bullseye" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          A dedicated workflow node that combines AI-powered message classification with workflow branching in a single step. Define up to 10 intents with natural language descriptions, and the node classifies user messages and routes to the matching branch automatically — replacing the previous TEXT\_UNDERSTANDING + Condition two-node pattern.

          <Frame>
            ![Intent Classification node](https://s3.eu-west-1.amazonaws.com/docx.flowx.ai/5.x/intent_classification_node.png)
          </Frame>

          <Card title="Documentation" icon="book" href="/5.9/ai-platform/agent-builder/intent-classification">
            See the complete Intent Classification documentation.
          </Card>
        </Tab>

        <Tab title="Key Features">
          <CardGroup cols={2}>
            <Card title="AI + routing in one node" icon="code-merge">
              Combines LLM classification and conditional branching — no separate Condition node needed
            </Card>

            <Card title="Natural language conditions" icon="message">
              Define intents as plain-text descriptions instead of code expressions
            </Card>

            <Card title="Conversation memory" icon="brain">
              Optionally use past conversation context for more accurate classification
            </Card>

            <Card title="Built-in fallback" icon="shield">
              Automatic "If No Intent Matches" branch handles unrecognized inputs
            </Card>
          </CardGroup>
        </Tab>
      </Tabs>

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

    ***

    ### **Navigate in UI Flow**

    <Card title="Navigate in UI Flow" icon="arrow-up-right-from-square" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          A new workflow node exclusive to **Chat Driven** (conversational) workflows. It navigates the user to a specific screen in a UI Flow, passing dynamic parameters — for example, the AI says *"Let me open your account details"* and the user sees a pre-filled form with data from the conversation.

          <Frame>
            ![Navigate in UI Flow node configuration](https://s3.eu-west-1.amazonaws.com/docx.flowx.ai/5.6/navigate_ui_flow_node.png)
          </Frame>

          <Card title="Documentation" icon="book" href="/5.9/ai-platform/conversational-workflows#navigate-in-ui-flow-node">
            See the Navigate in UI Flow section in Conversational Workflows.
          </Card>
        </Tab>

        <Tab title="Key Features">
          <CardGroup cols={2}>
            <Card title="Conversational context" icon="comments">
              Navigate users to UI screens directly from a Chat Driven workflow conversation
            </Card>

            <Card title="Dynamic parameters" icon="code">
              Pass workflow data to the destination screen using `${expression}` syntax
            </Card>

            <Card title="Destination picker" icon="map">
              Select from the UI Flow's navigation tree with auto-populated query parameters
            </Card>

            <Card title="Chat Driven only" icon="lock">
              Available exclusively in the Actions category of conversational workflows
            </Card>
          </CardGroup>
        </Tab>
      </Tabs>

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

    ***

    ### **Context Retrieval node**

    <Card title="Context Retrieval Node" icon="magnifying-glass" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          A dedicated workflow node that performs RAG (Retrieval-Augmented Generation) searches against Knowledge Bases without calling an LLM. Returns raw chunks with relevance scores and metadata, giving you full control over downstream processing. Supports hybrid, semantic, and keyword search with configurable re-ranking and metadata filters.

          Use Context Retrieval when you need to inspect, filter, or transform chunks before passing them to an LLM — for example, checking relevance scores before generating a response. For all-in-one RAG, use a Custom Agent node with a Knowledge Base attached instead.

          <Frame>
            ![Context Retrieval node configuration](https://s3.eu-west-1.amazonaws.com/docx.flowx.ai/5.6/context_retrieval_node.png)
          </Frame>

          <Card title="Documentation" icon="book" href="/5.9/ai-platform/agent-builder/context-retrieval">
            See the complete Context Retrieval documentation.
          </Card>
        </Tab>

        <Tab title="Key Features">
          <CardGroup cols={2}>
            <Card title="No LLM required" icon="bolt">
              Retrieves chunks directly — no AI generation step, lower latency and cost
            </Card>

            <Card title="Multiple search types" icon="magnifying-glass">
              Hybrid, semantic, or keyword search with configurable relevance thresholds
            </Card>

            <Card title="Metadata filters" icon="filter">
              Filter chunks by user-defined metadata for scoped retrieval
            </Card>

            <Card title="Re-ranking" icon="arrow-up-wide-short">
              Optional re-ranking for improved result ordering
            </Card>
          </CardGroup>
        </Tab>
      </Tabs>

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

    ***

    ### **Extract Data from File**

    <Card title="Extract Data from File" icon="file-magnifying-glass" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          The workflow node formerly known as "Extract Text from Document" has been renamed to **Extract Data from File** and gained three new configurable settings: **Extraction Method** (LLM Model, OCR Engine, or Text Parsing), **Image Extraction** (Image Description or Image Contents), and **Detect Signatures**. The node now also accepts image files (JPG, PNG, TIFF) in addition to documents.

          <Card title="Documentation" icon="book" href="/5.9/ai-platform/agent-builder/extract-data-from-file">
            See the complete Extract Data from File documentation.
          </Card>
        </Tab>

        <Tab title="Key Features">
          <CardGroup cols={2}>
            <Card title="Three extraction methods" icon="sliders">
              Choose between LLM Model (AI vision), OCR Engine (scanned docs), or Text Parsing (digital PDFs) per use case
            </Card>

            <Card title="Image support" icon="image">
              Process JPG, PNG, and TIFF files alongside PDF, DOCX, XLSX, and PPTX
            </Card>

            <Card title="Signature detection" icon="signature">
              Identify signature areas within documents when using LLM or OCR extraction
            </Card>

            <Card title="Moved to Tools category" icon="wrench">
              The node is now in the **Tools** category in the workflow node palette
            </Card>
          </CardGroup>
        </Tab>
      </Tabs>

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

    ***

    ### **Web Page Extractor**

    <Card title="Web Page Extractor" icon="globe" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          A new workflow node in the **Tools** category that collects readable content from web page URLs. Crawl documentation sites to build a Knowledge Base, scrape product pages for competitive analysis, or extract terms and conditions for compliance review. Supports static URL lists or dynamic URL generation, configurable crawling depth with link following, PDF extraction from linked documents, and adjustable scrape speed presets.

          <Frame>
            ![Web Page Extractor node configuration](https://s3.eu-west-1.amazonaws.com/docx.flowx.ai/5.6/web_page_extractor_node.png)
          </Frame>

          <Card title="Documentation" icon="book" href="/5.9/ai-platform/agent-builder/web-page-extractor">
            See the complete Web Page Extractor documentation.
          </Card>
        </Tab>

        <Tab title="Key Features">
          <CardGroup cols={2}>
            <Card title="Static or dynamic URLs" icon="link">
              Provide a fixed list of up to 20 URLs or generate them dynamically from workflow data
            </Card>

            <Card title="Link following" icon="diagram-project">
              Follow links on pages up to a configurable depth (0–10 levels)
            </Card>

            <Card title="PDF processing" icon="file-pdf">
              Extract content from PDF files linked on crawled pages
            </Card>

            <Card title="Speed presets" icon="gauge-high">
              Choose Slow, Moderate, Fast, or Custom with manual rate limit and concurrency
            </Card>
          </CardGroup>
        </Tab>
      </Tabs>

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

  <Tab title="Integrations">
    Connect FlowX to more systems — trigger processes from external events, route traffic through proxies, and query your own MongoDB databases.

    🔗 [**Incoming Webhooks**](#incoming-webhooks) - Trigger processes from external HTTP POST requests\
    🛡️ [**Proxy Server Connections**](#proxy-server-connections) - Route integration traffic through proxy servers\
    🗄️ [**Unmanaged MongoDB Datasource**](#unmanaged-mongodb-datasource) - Connect to externally managed MongoDB instances\
    📧 [**Email Trigger Enhancements**](#email-trigger-enhancements) - Resource management, reply-to, and mock email testing\
    🔐 [**MCP Authentication**](#mcp-authentication) - BEARER and BASIC auth support for MCP server connections\
    📜 [**Base64 Certificate Support**](#base64-certificate-support) - Provide certificates as base64-encoded strings instead of file paths\
    📊 [**CSV/Excel to JSON Conversion**](#csvexcel-to-json-conversion) - Download CSV and Excel files as structured JSON on the fly

    ### **Incoming Webhooks**

    <Card title="Incoming Webhooks" icon="webhook" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          A new data source type and microservice (`webhook-gateway`) that allows external systems to trigger FlowX processes via HTTP POST requests. Create a Webhook data source in Integration Designer, connect it to a Message Start Event in your process, and FlowX generates a unique URL with API key authentication. When external systems POST to this URL, a process instance starts automatically with the webhook payload and headers.

          <Frame>
            ![Active webhook trigger in Manage Triggers](https://s3.eu-west-1.amazonaws.com/docx.flowx.ai/5.6/webhook_trigger_active.png)
          </Frame>

          <Note>
            Requires deploying the new `webhook-gateway` microservice. See [Deployment Guidelines](./deployment-guidelines-v5.6) for configuration.
          </Note>

          <Card title="Documentation" icon="book" href="/5.9/docs/platform-deep-dive/integrations/incoming-webhooks">
            See the complete Incoming Webhooks documentation.
          </Card>
        </Tab>

        <Tab title="Key Features">
          <CardGroup cols={2}>
            <Card title="API key authentication" icon="key">
              Each webhook gets a unique, cryptographically secure API key for authentication
            </Card>

            <Card title="JSON payload forwarding" icon="code">
              Webhook body and headers are forwarded to the process instance as variables
            </Card>

            <Card title="Manage Triggers integration" icon="toggle-on">
              Activate, deactivate, and monitor webhooks from the Manage Triggers UI
            </Card>

            <Card title="API key regeneration" icon="rotate">
              Regenerate API keys without recreating the webhook configuration
            </Card>
          </CardGroup>
        </Tab>
      </Tabs>

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

    ***

    ### **Proxy Server Connections**

    <Card title="Proxy Server Connections" icon="shield-halved" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          Create reusable proxy connections in Integration Designer and attach them to RESTful System data sources. Route outbound API traffic through HTTP or HTTPS proxy servers for environments that require intermediary routing for security or compliance.

          <Frame>
            ![Proxy Connection configuration example](https://s3.eu-west-1.amazonaws.com/docx.flowx.ai/5.6/proxy_connections_example.png)
          </Frame>

          <Card title="Documentation" icon="book" href="/5.9/docs/platform-deep-dive/integrations/proxy-connections">
            See the complete Proxy Connections documentation.
          </Card>
        </Tab>

        <Tab title="Key Features">
          <CardGroup cols={2}>
            <Card title="HTTP and HTTPS proxies" icon="lock">
              Configure HTTP or HTTPS proxy servers with optional basic authentication
            </Card>

            <Card title="Reusable connections" icon="arrows-rotate">
              Create a proxy once and attach it to multiple RESTful System data sources
            </Card>

            <Card title="Test connectivity" icon="check">
              Validate proxy configuration before saving with the built-in test function
            </Card>

            <Card title="Config parameter support" icon="gear">
              Use `${param}` syntax in host and port fields for environment-specific values
            </Card>
          </CardGroup>
        </Tab>
      </Tabs>

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

    ***

    ### **Unmanaged MongoDB Datasource**

    <Card title="Unmanaged MongoDB Datasource" icon="database" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          Connect to externally managed MongoDB instances as a data source in FlowX. Unlike the built-in FlowX Database (which provisions and manages MongoDB collections automatically), Unmanaged MongoDB connects to databases and collections you control — with the same CRUD operations, connection discovery, and configurable connection pooling. Requires MongoDB 6.0 or later.

          <Frame>
            ![Unmanaged MongoDB data source configuration](https://s3.eu-west-1.amazonaws.com/docx.flowx.ai/5.6/unmanaged_mongo.png)
          </Frame>

          <Card title="Documentation" icon="book" href="/5.9/docs/platform-deep-dive/integrations/unmanaged-mongodb">
            See the complete Unmanaged MongoDB documentation.
          </Card>
        </Tab>
      </Tabs>

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

    ***

    ### **Email Trigger Enhancements**

    <Card title="Email Trigger Enhancements" icon="envelope" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          FlowX.AI 5.6.0 enhances the Email Trigger with resource management capabilities, reply-to-email support, process instance tracking for email-triggered processes, and mock email testing for development.

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

        <Tab title="Key Features">
          <CardGroup cols={2}>
            <Card title="Resource management" icon="folder-open">
              Manage email trigger resources with proper lifecycle controls
            </Card>

            <Card title="Reply-to-email" icon="reply">
              Support for reply-to patterns in email-triggered workflows
            </Card>

            <Card title="Process instances" icon="list-check">
              View and track process instances created from email triggers
            </Card>

            <Card title="Mock email testing" icon="vial">
              Test email-triggered processes with mock email content during development
            </Card>
          </CardGroup>
        </Tab>
      </Tabs>

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

    ***

    ### **MCP Authentication**

    <Card title="MCP Authentication" icon="key" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          MCP server connections now support **BEARER** and **BASIC** authentication methods. Configure auth credentials when adding an MCP data source to connect to secured MCP servers.

          <Card title="Documentation" icon="book" href="/5.9/docs/platform-deep-dive/integrations/mcp-integration/adding-mcp-data-source">
            See the Adding MCP Data Source documentation.
          </Card>
        </Tab>
      </Tabs>

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

    ***

    ### **Base64 Certificate Support**

    <Card title="Base64 Certificate Support" icon="file-certificate" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          RESTful system data sources now support providing keystore and truststore content as **base64-encoded strings** instead of file paths. A new "Certificate type" selector lets you choose between Base64 (default for new configurations) and Path (existing behavior). Additionally, keystore and truststore passwords now support `${configParam}` placeholder syntax for dynamic per-environment resolution.

          <Frame>
            ![Certificate type selector with Base64 and Path options](https://s3.eu-west-1.amazonaws.com/docx.flowx.ai/5.6/certificate_type_selector.png)
          </Frame>

          <Card title="Documentation" icon="book" href="/5.1/docs/platform-deep-dive/integrations/integration-designer#certificates">
            See the Integration Designer certificates documentation.
          </Card>
        </Tab>
      </Tabs>

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

    ***

    ### **CSV/Excel to JSON Conversion**

    <Card title="CSV/Excel to JSON Conversion" icon="file-csv" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          Download CSV, XLS, or XLSX files as structured JSON directly from the file download endpoints. The conversion happens on the fly using the `Accept: application/json` header — no new files are created in storage. Supports two output formats: an array of objects (one per row) or a columnar structure.

          <Card title="Documentation" icon="book" href="/5.1/docs/platform-deep-dive/core-extensions/content-management/documents-plugin/converting-documents-to-different-formats#csvexcel-to-json-conversion">
            See the Document Conversion documentation.
          </Card>
        </Tab>
      </Tabs>

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

  <Tab title="UI & Designer">
    Richer end-user experiences with session state, chat history, and navigation — plus Designer productivity improvements.

    🗺️ [**UI Flow Route Management**](#ui-flow-route-management) - Configure routes, query parameters, and navigation in UI Flows\
    ▶️ [**UI Flow Start Parameters**](#ui-flow-start-parameters) - Pass parameters when starting UI Flows\
    💾 [**UI Flow Session Variables**](#ui-flow-session-variables) - Persist data across pages from workflows and file uploads\
    📋 [**Chat History**](#chat-history) - Browse and resume past chat conversations\
    💡 [**Chat Suggested Prompts**](#chat-suggested-prompts) - Pre-configured prompt suggestions in chat empty state\
    🖱️ [**onClick UI events**](#onclick-ui-events) - Client-side data updates on Button and Collection Prototype clicks\
    ✨ [**Monaco Editor Autocomplete**](#monaco-editor-autocomplete) - Autocomplete from config params in code editors\
    📊 [**KB query results in workflow console**](#kb-query-results-in-workflow-console) - View retrieved chunks and relevance scores during workflow runs\
    📎 [**Multi-file bulk upload**](#multi-file-bulk-upload) - Upload multiple files simultaneously\
    ❌ [**DISMISS UI action**](#dismiss-ui-action) - Dismiss modals automatically after Start Workflow completes\
    🎨 [**Process Variables UX**](#process-variables-ux-improvements) - UI/UX improvements for updating process variables\
    🏷️ [**Enum label display**](#enum-label-display) - Show enum labels instead of codes in text components\
    📬 [**Notification template usages**](#notification-template-usages) - See where notification templates are used\
    📐 [**Side Panel in Data Model**](#side-panel-in-data-model) - Improved data model navigation with side panel\
    👁️ [**On Display UI event**](#on-display-ui-event) - Re-trigger actions every time a screen becomes visible\
    🪟 [**On Load event on Modal**](#on-load-event-on-modal) - Modal components now support On Load events\
    🏗️ [**KB user-defined metadata**](#kb-user-defined-metadata) - Define custom metadata keys on Knowledge Base content sources\
    ⚙️ [**Config params in workflow conditions**](#config-params-in-workflow-conditions) - Use config params and user details in workflow Fork node expressions\
    🎨 [**Branding settings grouping**](#branding-settings-grouping) - Reorganized branding settings page\
    ✍️ [**Markdown in chat messages**](#markdown-in-chat-messages) - Render formatted text, links, and lists in chat responses\
    🔗 [**External Action dynamic URL**](#external-action-dynamic-url) - Use expressions in External Action URLs for dynamic navigation\
    📬 [**Notification history**](#notification-history) - View sent notification details and search by process instance

    ### **UI Flow Route Management**

    <Card title="UI Flow Route Management" icon="route" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          Define query parameters on root views (Pages, Modals), pass data between screens via URL query strings, and get automatic breadcrumb generation from the navigation graph. Navigate To actions support destination parameter mapping with `${expression}` syntax for dynamic values.

          <Frame>
            ![Route parameters modal with URL path preview](https://s3.eu-west-1.amazonaws.com/docx.flowx.ai/5.6/route_parameters_modal.png)
          </Frame>

          <Card title="Documentation" icon="book" href="/5.9/docs/building-blocks/ui-flows#route-management">
            See the Route Management section in UI Flows.
          </Card>
        </Tab>

        <Tab title="Key Features">
          <CardGroup cols={2}>
            <Card title="Route parameters" icon="map">
              Define named query parameters on root views with default values and required flags
            </Card>

            <Card title="Parameter passing" icon="code">
              Map data from process store to destination query parameters using JSON expressions
            </Card>

            <Card title="Auto breadcrumbs" icon="ellipsis">
              Breadcrumbs auto-generate from the navigation graph with proper parameter handling
            </Card>

            <Card title="Modal URL state" icon="window-maximize">
              Modals add `modalId` to URL — survives page reload and supports deep linking
            </Card>
          </CardGroup>
        </Tab>
      </Tabs>

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

    ***

    ### **UI Flow Start Parameters**

    <Card title="UI Flow Start Parameters" icon="play" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          Pass initial data when launching a UI Flow. Define start parameters as a JSON object in the Designer's Run dialog, extract them from URL query strings in SaaS container apps, or send them in the API request body. Parameters are persisted on the session and available throughout the UI Flow lifecycle.

          <Frame>
            ![Run UI Flow dialog with Start params JSON editor](https://s3.eu-west-1.amazonaws.com/docx.flowx.ai/5.6/ui_flow_start_params.png)
          </Frame>

          <Card title="Documentation" icon="book" href="/5.9/docs/building-blocks/ui-flows#start-parameters">
            See the Start Parameters section in UI Flows.
          </Card>
        </Tab>
      </Tabs>

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

    ***

    ### **UI Flow Session Variables**

    <Card title="UI Flow Session Variables" icon="database" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          UI Flow sessions can now persist variables across all pages sharing the same session ID. Data from start parameters, workflow outputs, and file upload responses is automatically collected and merged into session variables. Reference them in component configurations using `${}` syntax. A new **Variables** tab in the Designer session console shows current values for debugging.

          <Frame>
            ![Variables tab in UI Flow session console](https://s3.eu-west-1.amazonaws.com/docx.flowx.ai/5.6/ui_flow_session_variables.png)
          </Frame>

          <Card title="Documentation" icon="book" href="/5.9/docs/building-blocks/ui-flows#session-variables">
            See the Session Variables section in UI Flows.
          </Card>
        </Tab>
      </Tabs>

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

    ***

    ### **Chat History**

    <Card title="Chat History" icon="clock-rotate-left" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          Users can now browse and resume past chat conversations. Chat History displays a list of previous sessions grouped by time (Today, Yesterday, Previous 7 Days, Previous 30 Days, Older), with the ability to open any conversation and continue where they left off. Conversations are per-user with access control enforced.

          <Frame>
            ![Chat History panel with conversation list](https://s3.eu-west-1.amazonaws.com/docx.flowx.ai/5.6/chat_history.png)
          </Frame>

          <Card title="Documentation" icon="book" href="/5.9/ai-platform/chat-component#chat-history">
            See the Chat History section in Chat component.
          </Card>
        </Tab>
      </Tabs>

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

    ***

    ### **Chat Suggested Prompts**

    <Card title="Chat Suggested Prompts" icon="lightbulb" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          The Chat component now supports pre-configured **Suggested Prompts** — pill buttons displayed below the welcome message in the chat empty state. Configure a title and up to 5 prompt options in the Designer. When a user clicks a suggestion, it is submitted as their message, starting the conversation immediately.

          <Frame>
            ![Suggested Prompts in chat empty state](https://s3.eu-west-1.amazonaws.com/docx.flowx.ai/5.6/chat_suggested_prompts.png)
          </Frame>

          <Card title="Documentation" icon="book" href="/5.9/ai-platform/chat-component#suggested-prompts">
            See the Suggested Prompts section in Chat component.
          </Card>
        </Tab>
      </Tabs>

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

    ***

    ### **Monaco Editor Autocomplete**

    <Card title="Monaco Editor Autocomplete" icon="wand-magic-sparkles" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          Code editors in the Designer now provide autocomplete suggestions from your project's configuration parameters. This speeds up writing business rules and expressions that reference config params.

          <Card title="Documentation" icon="book" href="/5.1/docs/projects/runtime/configuration-parameters-overrides">
            See the Configuration Parameters documentation.
          </Card>
        </Tab>
      </Tabs>

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

    ***

    ### **Process Variables UX improvements**

    <Card title="Process Variables UX" icon="sliders" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          UI/UX improvements to the Update Process Variables experience, making it easier to view and edit runtime process data.

          <Card title="Documentation" icon="book" href="/5.9/docs/projects/runtime/active-process/update-process-variables">
            See the Update Process Variables documentation.
          </Card>
        </Tab>
      </Tabs>

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

    ***

    ### **onClick UI events**

    <Card title="onClick UI events" icon="hand-pointer" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          Buttons and Collection Prototypes now support **onClick** UI events — client-side JavaScript expressions that execute immediately when clicked, *before* any configured UI actions fire. Use them for instant local data updates without server roundtrips.

          <Card title="Documentation" icon="book" href="/5.9/docs/building-blocks/ui-designer/ui-events">
            See the UI Events documentation.
          </Card>
        </Tab>
      </Tabs>

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

    ***

    ### **KB query results in workflow console**

    <Card title="KB Query Results" icon="magnifying-glass" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          The workflow run console now includes a **Knowledge Base** tab that displays retrieved chunks, relevance scores, content sources, and metadata when Custom Agent nodes query a knowledge base. This makes it easier to debug and tune RAG-powered workflows.

          <Card title="Documentation" icon="book" href="/5.9/docs/platform-deep-dive/integrations/knowledge-base-integration/using-knowledge-base-in-workflows">
            See Using Knowledge Base in Workflows.
          </Card>
        </Tab>
      </Tabs>

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

    ***

    ### **Multi-file bulk upload**

    <Card title="Multi-file Bulk Upload" icon="files" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          Upload multiple files simultaneously at runtime using the new [Multiple File Upload](/5.1/docs/building-blocks/ui-designer/ui-component-types/multiple-file-upload) component. Supports drag-and-drop, batch selection, per-file validation, and progress tracking. Available in both process screens and UI Flows.
        </Tab>
      </Tabs>

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

    ***

    ### **DISMISS UI action**

    <Card title="DISMISS Action" icon="xmark" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          The Start Workflow UI action now includes a **Dismiss modal** checkbox. When enabled, the modal closes automatically after the workflow completes — removing the need for a separate close action.
        </Tab>
      </Tabs>

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

    ***

    ### **Enum label display**

    <Card title="Enum Label Display" icon="tag" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          Text components can now display the human-readable **label** of an enumeration value instead of the raw code. When a data key references an enumeration, the renderer resolves the selected code to its label at display time. Enumeration values are also prefetched from the data model before action resolution for improved performance.

          <Card title="Documentation" icon="book" href="/5.1/docs/platform-deep-dive/core-extensions/content-management/enumerations">
            See the Enumerations documentation.
          </Card>
        </Tab>
      </Tabs>

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

    ***

    ### **Notification template usages**

    <Card title="Notification Template Usages" icon="bell" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          Notification templates now show a **usages** modal that lists all processes and workflows referencing the template. This helps you understand the impact of changes before editing or deleting a template.

          <Card title="Documentation" icon="book" href="/5.1/docs/platform-deep-dive/core-extensions/content-management/notifications-plugin/managing-notification-templates">
            See the Managing Notification Templates documentation.
          </Card>
        </Tab>
      </Tabs>

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

    ***

    ### **Side Panel in Data Model**

    <Card title="Side Panel in Data Model" icon="sidebar" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          The Data Model editor now includes a side panel for easier navigation and editing of data model attributes, improving the workflow when working with large data models.
        </Tab>
      </Tabs>

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

    ***

    ### **On Display UI event**

    <Card title="On Display UI event" icon="eye" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          A new `onDisplay` event type that triggers every time a screen becomes visible — on initial load, when navigating back, or when a modal is dismissed. Unlike On Load (which fires once), On Display re-triggers on every view, making it ideal for refreshing data.

          Supported on Page, Zone, and Tab Bar components in UI Flows.
        </Tab>
      </Tabs>

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

    ***

    ### **On Load event on Modal**

    <Card title="On Load event on Modal" icon="window-restore" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          Modal components in UI Flows now support the On Load event and Start Workflow action. This enables data fetching when a modal opens, allowing you to load context-specific data for modal content.
        </Tab>
      </Tabs>

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

    ***

    ### **KB user-defined metadata**

    <Card title="KB user-defined metadata" icon="tags" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          Define custom metadata keys on Knowledge Bases and assign values to content sources. User-defined metadata enables filtering and scoping when searching chunks — for example, by department, document version, or region. Metadata values are propagated to the vector database and can be used as filters in the Context Retrieval workflow node.
        </Tab>
      </Tabs>

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

    ***

    ### **Config params in workflow conditions**

    <Card title="Config params in workflow conditions" icon="code-branch" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          Workflow Fork (condition) nodes can now access configuration parameters via `additionalData.applicationConfiguration` and authenticated user details via `additionalData.securityDetails` in their expressions. This enables environment-aware routing and user-based branching in integration workflows.
        </Tab>
      </Tabs>

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

    ***

    ### **Branding settings grouping**

    <Card title="Branding settings grouping" icon="palette" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          The branding settings page has been reorganized with improved grouping and layout, making it easier to find and configure branding options.
        </Tab>
      </Tabs>

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

    ***

    ### **Markdown in chat messages**

    <Card title="Markdown in Chat Messages" icon="markdown" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          Chat message components in web renderers now support Markdown rendering. AI-generated responses can include formatted text, headings, links, code blocks, and lists — displayed with proper styling in the chat interface.
        </Tab>
      </Tabs>

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

    ***

    ### **External Action dynamic URL**

    <Card title="External Action Dynamic URL" icon="arrow-up-right-from-square" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          External Action URLs now support `${expression}` syntax for dynamic values. Build destination URLs using process data, config params, or computed values — enabling context-aware external navigation from UI Flows.

          <Card title="Documentation" icon="book" href="/5.1/docs/building-blocks/ui-designer/ui-actions#external">
            See the UI Actions documentation.
          </Card>
        </Tab>
      </Tabs>

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

    ***

    ### **Notification history**

    <Card title="Notification History" icon="clock-rotate-left" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          New REST API endpoints on the notification plugin let you retrieve sent notification history. Query a paginated summary list filtered by app and optionally by process instance, or fetch full notification details by ID — including recipients, subject, body, and the source process/action that triggered it.

          * `GET /api/notification/summary` — paginated summary list with filtering and sorting
          * `GET /api/notification/{id}` — full notification details including body and recipients
        </Tab>

        <Tab title="Key Features">
          <CardGroup cols={2}>
            <Card title="Summary and detail views" icon="list">
              Paginated summary list for browsing, with full detail drill-down by notification ID
            </Card>

            <Card title="Source tracking" icon="magnifying-glass">
              Each notification records which process, node, and action triggered it for full traceability
            </Card>
          </CardGroup>
        </Tab>
      </Tabs>

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

  <Tab title="SaaS">
    User management and branding improvements for SaaS deployments.

    👤 [**Runtime User Invitations**](#runtime-user-invitations) - Invite runtime users directly to test projects\
    🏢 [**Workspace Type Display**](#workspace-type-display) - See workspace type within Designer\
    🎨 [**Container App Branding**](#container-app-branding) - Customize branding for SaaS container apps\
    👥 [**Designer User Invitations**](#designer-user-invitations) - Updated invite modal for designer users

    ### **Runtime User Invitations**

    <Card title="Runtime User Invitations" icon="user-plus" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          Invite runtime users directly to test projects from within the Designer. Simplifies the process of granting test access without requiring full workspace-level permissions.

          <Card title="Documentation" icon="book" href="/5.9/docs/saas/inviting-users">
            See the Inviting Users documentation.
          </Card>
        </Tab>
      </Tabs>

      <Badge color="blue" icon="cloud">SaaS</Badge>
    </Card>

    ***

    ### **Workspace Type Display**

    <Card title="Workspace Type Display" icon="building" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          The Designer now displays the workspace type (development, staging, production) directly within the workspace view, making it easier to identify your current environment.
        </Tab>
      </Tabs>

      <Badge color="blue" icon="cloud">SaaS</Badge>
    </Card>

    ***

    ### **Container App Branding**

    <Card title="Container App Branding" icon="paintbrush" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          Customize your SaaS container app branding at the organization level — upload a custom logo, set primary and secondary colors, toggle the header, and configure the solutions page background.

          <Card title="Documentation" icon="book" href="/5.9/docs/saas/container-app-branding">
            See the Container App Branding documentation.
          </Card>
        </Tab>
      </Tabs>

      <Badge color="blue" icon="cloud">SaaS</Badge>
    </Card>

    ***

    ### **Designer User Invitations**

    <Card title="Designer User Invitations" icon="users" iconType="duotone">
      <Tabs>
        <Tab title="Overview">
          The invite modal for designer users has been redesigned with clearer role selection, group assignment, and a streamlined layout for inviting multiple users.

          <Card title="Documentation" icon="book" href="/5.9/docs/saas/inviting-users">
            See the Inviting Users documentation.
          </Card>
        </Tab>
      </Tabs>

      <Badge color="blue" icon="cloud">SaaS</Badge>
    </Card>
  </Tab>

  <Tab title="Bug Fixes">
    ## Bug fixes

    ### Core Platform

    * **Authorization-system Oracle DB startup** — Fixed an issue where the authorization-system service failed to start when using Oracle as the configured database.
    * **Process definition merge timing** — Fixed a race condition where the process definition was updated before the merge was finalized.
    * **Theme import with builds** — Fixed an issue where themes were not included when importing builds.
    * **Library import permissions** — Fixed an issue where importing a library into a workspace redirected to a 403 error page.
    * **App version reimport** — Fixed an error that occurred when reimporting an app version (project or library).
    * **Email resend after URL expiry** — Fixed an issue where the resend email endpoint returned 200 OK but no email was sent after the URL expired.
    * **Platform status discovery** — Fixed an authorization error when trying to force discover platform status.
    * **Runtime roles in permissions** — Fixed inconsistent runtime roles display in the permissions dropdown.

    ### AI Platform & Workflows

    * **gRPC thread pool sizing** — Fixed under-provisioned gRPC client thread pools that caused socket timeouts and dropped requests in production.
    * **API error trace IDs** — API errors now include a reference to the active traceID for easier debugging.
    * **Cross-project resource copy** — Fixed an issue where copying a workflow resource to another project did not include LDM objects.
    * **Multi-instance mappings** — Fixed a 400 error when saving multi-instance mappings in data mappers.
    * **Email trigger mock testing** — Fixed errors when starting a process from a build with mock email content.
    * **Multiple start nodes with email trigger** — Fixed an issue where only one start option was displayed when a process contained multiple start nodes with email triggers.

    ### Renderers & UI

    * **Angular input field crash** — Fixed an issue where pressing Enter in an input field caused the Angular UI to crash.
    * **Floating Chat interaction blocking** — Fixed an issue where the floating chat component blocked all interaction with page content while open.
    * **S3 internal bucket error** — Fixed an error when the integration-designer downloads files from document-plugin via downloadPath.
    * **File upload second attempt** — Fixed an issue where upload requests were not made when uploading a second file.
    * **UI Flow analytics** — Fixed issues where analytics events were not visible and not saved for Navigate-to action types.
    * **Task management column selection** — Fixed an issue where the Last Updated column remained selected in task management.
    * **Task Manager theming and UX** — Multiple fixes for Task Manager theming, dropdown display, comment field styling, and user assignment behavior.
    * **Toggle/checkbox label alignment** — Fixed an issue where the switch toggle/checkbox or label shifted position when in an error state. {/* ZD-1170, RPT-5043 */}
    * **Query parameters lost after refresh** — Fixed an issue where URL query parameters were lost after page refresh in UI Flows. {/* RPT-5012 */}
    * **SSE connection management** — Fixed multiple issues where SSE connections were opened twice or not closed properly after messages were received. {/* RPT-5013, RPT-5007, RPT-5006 */}
    * **Modal layering** — Fixed incorrect layering when a loader modal was displayed on top of another modal. {/* RPT-4981 */}
    * **Card theming overrides** — Fixed an issue where card theming overrides were not applied when the card was collapsed. {/* RPT-5052 */}
    * **On Display workflow triggering** — Fixed an issue where past On Display workflows were not re-triggered on page refresh. {/* RPT-5025 */}

    ### Knowledge Base

    * **KB metadata handling** — Fixed multiple issues with Knowledge Base user-defined metadata: empty properties on content source creation, metadata not available for content sources added through apps, and incorrect cleanup when deleting metadata keys. {/* MT-2508, MT-2511, MT-2542 */}
  </Tab>

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

    ### At a glance

    This release includes **30+ new features and enhancements** across AI Platform, Integrations, UI & Designer, and SaaS — plus **28 bug fixes** spanning Core Platform, AI/Workflows, Renderers, and Knowledge Base.

    ***

    ### Deployment information

    <Info>
      For detailed deployment guidelines, see the [Deployment Guidelines v5.6.0](./deployment-guidelines-v5.6).
    </Info>

    For new environment variables and Kafka topics, see the [Deployment Guidelines v5.6.0](./deployment-guidelines-v5.6#new-environment-variables).

    ### Changes to be aware of

    <Info>
      FlowX.AI 5.6.0 is a SaaS-managed release — deployment-level changes (infrastructure, Kafka topics, service configuration) are handled automatically by FlowX. The items below are listed for transparency and for future reference when on-prem support ships in 5.7+.
    </Info>

    #### API change (action required if you use this endpoint)

    <Warning>
      **Process definition start metadata endpoint renamed** — `GET /api/process-definition/{uuid}/get-input-json` has been renamed to `GET /api/process-definition/{uuid}/get-start-metadata`. Update any API clients or custom integrations that call this endpoint directly.

      The response now includes an additional `hasEmailTriggerStart` boolean field.
    </Warning>

    #### Infrastructure changes (managed by FlowX on SaaS)

    * **gRPC thread pool configuration** — Default gRPC client thread pool sizes have been updated for better production throughput.
    * **WorkspaceCreatedEvent ownership** — Kafka topic ownership moved from `authorization-system` to `organization-manager`.

    {/* Not in 5.6.0: PLAT-1137/1140 (ES→MongoDB migration), PLAT-1373 (static models as OCI volumes) */}

    ### Compatibility

    <CardGroup cols={2}>
      <Card title="Upgrade path" icon="arrow-up-right-dots">
        Upgrade from v5.5.0 — if you call `get-input-json` directly, update to `get-start-metadata`. All other changes are managed automatically on SaaS.
      </Card>

      <Card title="Component versions" icon="circle-check" href="./deployment-guidelines-v5.6#component-versions">
        See the Deployment Guidelines for the full component version matrix
      </Card>
    </CardGroup>
  </Tab>
</Tabs>
