Skip to main content

Flowable 2025.1.x Release Notes

Initial release 2025.1.01, July 17, 2025

Introduction​

The Flowable product comprises:

  • Flowable Work, a process and case management platform with an out-of-the-box user interface.
  • Flowable AI Studio, an agentic case platform that allows you to build AI-driven solutions.
  • Flowable Engage, built on top of Flowable Work, adding conversations and external connectivity to WeChat, Whatsapp and others.
  • Flowable Design, a modeling environment to create BPMN, CMMN, DMN, Form and other model types that run in Platform/Work/Engage.
  • Flowable Control, an administration tool that can be used to manage the Flowable Platform / Work / Engage environments.
  • Flowable Inspect, a debugging and test component that can be used with Flowable Work and Engage.

These products are built on top of the Flowable Open Source project which can be found at Github.

Documentation​

The Flowable Open Source project also has extensive documentation available which can be found at https://www.flowable.com/open-source/docs/oss-introduction.

Highlights​

New versioning pattern​

A new versioning pattern has been introduced with the major version now including the year of the release and the an incremental version identifier. With this first release the major version is 2025.1 and the next major version in December will have 2025.2. The last part of the versioning pattern shows the minor version starting with 01. So therefore the full version identifier is 2025.1.01 for this release and a new service pack will be 2025.1.02 and further. Note that this is a change in the versioning pattern and not an indicator of breaking changes compared to the last major version 3.17.x. Also note that the Java artefact version is 2025.1.01, but the NPM version for the frontend components use version 2025.1.1 because the 01 is not allowed for NPM packages. More information can be found in your Flowable support portal.

Flowable AI Studio​

  • Introduced a new AI agent model type with orchestrator, document, utility and external agent sub types as option to facilitate for different usage of AI.

  • Introduced an orchestrator agent that provides autonomous and suggestion capabilities to execute activities in a case. It uses internal MCP logic to determine possible next steps based on the trigger origin, the state of a case etc. The choice between autonomous or suggestion based execution of activities can be made per activity in a case model, bringing full flexibility and letting the model define the level of autonomous execution.

  • An new agent task can be used in Case and Process models to interact with a LLM to execute user defined prompts than can be enhanced with the Case and Process state information.

  • Added support for Retrieval-Augmented Generation (RAG) models to use document content in the AI agent interaction.

  • Introduced a new chat component in Flowable Work that allows a user to interact with the case information. For example, a short summary about the case history can be requested, but also suggestions can be made by Flowable on which activities are advised to perform next.

  • Every interaction with an agent, independent of the agent type, is stored in a new agent exchange table. This provides a full audit trail of the interaction with an AI service.

  • Introduced an option to switch between different LLMs based on the requirements of the Case and Process model.

  • Added support for external AI agents, including AWS Bedrock, Azure AI agents and SalesForce agents.

  • Introduced a new AI agent model editor in Flowable Design with orchestrator, document, utility and external agent sub types as option to facilitate for different usage of AI. You can define operations similar to the service model editor and have structured or text based input and output definitions and a prompt definition. You can also choose the LLM and AI vendor that you want to work with as part of the agent model. This makes it possible to use different LLMs and AI vendors for different use cases.

  • Improved the testing of agent models in Flowable Design to see the response structure of a prompt in a quick manner.

  • Added a new Agent engine in Flowable Control with deployments, definition and instance search and detail views. On an agent instance level you also have access to all the agent exchange messages that are sent and received from the AI service interactions.

Flowable Work​

  • Added support for PowerAutomate Desktop to be used for RPA tasks as part of a case or process execution.

  • Added support for using content item types in data dictionary objects, to provide easy access to one or more documents within a data structure.

  • Added a global search functionality to search for work instances and tasks based on the name and description. It's also possible to define variable values as part of the ES mapping definition to be considered for search.

  • The introduction of the new global search functionality also introduced a top bar. The user profile and getting access to settings and Inspect (when enabled) etc, is now available in the top right of the Work view instead of the left bottom.

  • Introduced a global date formatting configuration that allows for consistent date formatting throughout the application, when a specific date format is required.

  • Performance improvements have been implemented to support a better user experience when editing a large form.

  • Improved the usability and styling of the data table component and added more filtering capabilities. The underlying table framework has been upgraded and if needed the legacy data table can still be activated with flowable.frontend.features.legacyDataTable=true.

  • Added support to define background colors based on expressions for a data table column.

  • Added support for large numbers, including decimals, to allow for numeric values of for example 17 digits to be used in a form input.

  • Improved the performance of indexing large hierarchies of case, sub process and task instances.

  • Implemented a new incident configuration option that adds a new incident entity for every exception that occurs in the Flowable Engines. This can be used in Flowable Control to check for issues with the case or process execution.

  • Added a feature to be able to define secret values in Flowable Control and use these in for example the authentication configuration of a service model in Flowable Design. With this secret values like tokens can be stored safely outside of a model.

  • Added a feature to be able to define OAuth client configurations in Flowable Control and use these for authentication configuration of a service model in Flowable Design.

  • Added support for a user event listener button that can be added to a work and case page task form to trigger a user event listener of a case model.

  • Added support to update data object variable values through the Platform REST API.

Flowable Design​

  • Added a global search functionality to search for workspaces, apps and models.

  • Multi edit support has been added to allow for editing the same attribute value for multiple elements having this attribute, at the same time. You can select multiple elements in the Case, Process and Form editors and change the shared attributes for all selected elements.

  • In the data dictionary editor a new content item type has been added to include content items in a data dictionary object structure.

  • Added a feature to use secret values for the authentication config of a service model.

  • Improved the user experience for the service, data object, action and other model editors.

  • Added a new PowerAutomate task to the case and process editor palette.

  • Added a new user event listener button to the form editor palette to be able to trigger a user event listener of a case in a work, case page task or task form.

Flowable Control​

  • Improved the case and process migration usability.

  • Added a feature to define secret values.

  • Added a feature to define OAuth clients.

  • Added support to update data object variable values.

Flowable Cloud​

  • In addition to the Flowable on premise offering, Flowable also provides a Flowable Cloud offering:

    • Flowable Cloud Dedicated for a private cloud solution, managed by Flowable with lots of flexibility for your use cases.

    • Flowable Cloud Shared is available as a multi tenant environment that uses a shared database and shared Flowable environment, with full tenant isolation.

  • You can find more information on our Flowable Cloud website page.

  • The following features describe new functionality that has been added to the Flowable Cloud Shared offering:

    • A new application named Flowable Hub, where customers can self-service their tenant with managing users, groups and permissions has been introduced. In addition, apps, work instances, tasks, jobs, incidents and more can be searched, viewed and have actions that can be performed. The actions include, case and process migration, setting or changing variable values, editing task details and rescheduling a deadletter job.

    • Implemented a remote scripting execution option with Azure functions. This provides a safe and isolated environment to run scripting logic in a seamless way.

    • Implemented a SSO integration so that external identity providers can be configured to be used for a specific tenant and authentication will be done against the configured external identity provider.

    • Implemented a new incident configuration option that adds a new incident entity for every exception that occurs in the Flowable Engines. This can be used in Flowable Hub to check for issues with the case or process execution.

    • Added a feature to define secret values in Flowable Hub and use these in for example the authentication configuration of a service model in Flowable Design. In this was secret values like tokens can be stored safely outside of a model.

    • Added a feature to define oAuth2 client configurations in Flowable Hub and use these for authentication configuration of a service model in Flowable Design.

Upgrade information​

Work Upgrade information​

  • The Flowable Open Source JUnit 3 and 4 support has been deprecated. It will be removed in the next release.

  • The use of joda-time has been deprecated. It will be removed in the next release. There will be a warning logged when using joda-time types as a variable.

Spring Boot​

  • Flowable has been upgraded to Spring Boot 3.5.3.

Pentest report​

  • A new pentest has been performed on Flowable Work and Flowable Design and the results are available via your Flowable account manager or contact person.

AI Studio Database changes​

  • Added a new table FLW_AGENT_DEPLOYMENT to store the agent model deployment information.

  • Added a new table FLW_AGENT_DEPLOYMENT_RES to store the agent model deployment resources.

  • Added a new table FLW_AGENT_DEFINITION to store the agent definition information.

  • Added a new table FLW_AGENT_INSTANCE to store information about agents that are currently running.

  • Added a new table FLW_AGENT_INSTANCE_EXCHANGE to store information about all the exchanges with the AI services that happen as part of an agent execution that is running.

  • Added a new table FLW_HI_AGENT_INSTANCE to store information about agents that are running or are completed.

  • Added a new table FLW_HI_AGENT_INSTANCE_EXCHANGE to store information about all the exchanges with the AI services agents that happen as part of an agent execution that is running or is completed.

  • Added a new table FLW_AGENT_KB_DEFINITION to store the knowledge base definition information.

  • Added a new table FLW_AGENT_KB_ITEM to store information about a knowledge base item.

  • Added a new table FLW_AGENT_KB_ITEM_SECTION to store information about a section of a knowledge base item.

  • Added a new table FLW_HI_AGENT_INSTANCE_KB_LINK to store the link between an agent execution and the knowledge base.

  • Added a new table FLW_AGENT_KB_DEF_METADATA to store meta data information for a knowledge base definition.

Work Database changes​

  • Added a new foreign key constraint on FLW_PL_DEPLOYMENT_RESOURCE from the DEPLOYMENT_ID_ column to the ID_ column of the FLW_PL_DEPLOYMENT table.

  • Added new index on column DEPLOYMENT_ID_ of table FLW_PL_DEPLOYMENT_RESOURCE with name FLW_IDX_PL_RSRC_DPL.

  • Added new index on columns REGISTRATION_KEY_ and TENANT_ID_ of table FLW_OAUTH_CLIENT_REG with name IDX_FLW_OAUTH_CL_REG_KEY_TEN.

  • Dropped not null constraint on column CLIENT_ID_ of table FLW_OAUTH_CLIENT_REG.

  • Added columns ROOT_SCOPE_ID_, ROOT_SCOPE_TYPE_, ROOT_SCOPE_DEFINITION_ID_, ROOT_SCOPE_DEFINITION_KEY_, SCOPE_DEFINITION_KEY_ and ELEMENT_ID_ to the ACT_APP_INCIDENT table.

  • Added new index on column ROOT_SCOPE_DEFINITION_KEY_ of table ACT_APP_INCIDENT with name ACT_IDX_APP_INC_DEF_ROOT_KEY.

  • Added new index on column SCOPE_DEFINITION_KEY_ of table ACT_APP_INCIDENT with name ACT_IDX_APP_INC_DEF_KEY.

  • Added new index on columns ROOT_SCOPE_DEFINITION_KEY_ and TENANT_ID_ of table ACT_APP_INCIDENT with name ACT_IDX_APP_INC_ROOT_K_TENANT.

  • Added new index on columns SCOPE_DEFINITION_KEY_ and TENANT_ID_ of table ACT_APP_INCIDENT with name ACT_IDX_APP_INC_DEF_KEY_TENANT.

  • Added new index on columns ROOT_SCOPE_ID_ and ROOT_SCOPE_TYPE_ of table ACT_APP_INCIDENT with name ACT_IDX_APP_INC_ROOT_SCOPE.

  • Added a new foreign key constraint on FLW_FO_FORM_RESOURCE from the DEPLOYMENT_ID_ column to the ID_ column of the FLW_FO_FORM_DEPLOYMENT table.

  • Added new index on column DEPLOYMENT_ID_ of table FLW_FO_FORM_RESOURCE with name FLW_IDX_FO_RSRC_DPL.

  • Added a new foreign key constraint on FLW_CO_DEPLOYMENT_RESOURCE from the DEPLOYMENT_ID_ column to the ID_ column of the FLW_CO_DEPLOYMENT table.

  • Added new index on column DEPLOYMENT_ID_ of table FLW_CO_DEPLOYMENT_RESOURCE with name FLW_IDX_CO_RSRC_DPL.

  • Added a new foreign key constraint on FLW_ACTION_DEPLOYMENT_RESOURCE from the DEPLOYMENT_ID_ column to the ID_ column of the FLW_ACTION_DEPLOYMENT table.

  • Added new index on column DEPLOYMENT_ID_ of table FLW_ACTION_DEPLOYMENT_RESOURCE with name FLW_IDX_ACTION_RSRC_DPL.

  • Added a new foreign key constraint on FLW_POLICY_DEPLOYMENT_RESOURCE from the DEPLOYMENT_ID_ column to the ID_ column of the FLW_POLICY_DEPLOYMENT table.

  • Added new index on column DEPLOYMENT_ID_ of table FLW_POLICY_DEPLOYMENT_RESOURCE with name FLW_IDX_POLICY_RSRC_DPL.

  • Added a new foreign key constraint on FLW_TEMPL_DEPLOYMENT_RESOURCE from the DEPLOYMENT_ID_ column to the ID_ column of the FLW_TEMPL_DEPLOYMENT table.

  • Added new index on column DEPLOYMENT_ID_ of table FLW_TEMPL_DEPLOYMENT_RESOURCE with name FLW_IDX_TEMPL_RSRC_DPL.

  • Added column USER_ACCOUNT_ID_ to the FLW_CONV_PARTICIPANT_REGISTRY table.

  • Change column type of REFERENCE_ID_ of the FLW_ENGAGE_MSG_REF_MAPPING table to support a text of 128 characters.

  • Added a new foreign key constraint on FLW_EVENT_RESOURCE from the DEPLOYMENT_ID_ column to the ID_ column of the FLW_EVENT_DEPLOYMENT table.

  • Added new index on column DEPLOYMENT_ID_ of table FLW_EVENT_RESOURCE with name FLW_IDX_EVENT_RSRC_DPL.

  • Added a new foreign key constraint on ACT_DMN_DEPLOYMENT_RESOURCE from the DEPLOYMENT_ID_ column to the ID_ column of the ACT_DMN_DEPLOYMENT table.

  • Added new index on column DEPLOYMENT_ID_ of table ACT_DMN_DEPLOYMENT_RESOURCE with name ACT_IDX_DMN_RSRC_DPL.

Design Database changes​

  • Change column type of PROMPT_ of the FLW_DE_MODEL_GENERATION table to support large text values.

Control Database changes​

  • No database changes.

Open Source Artifacts Dependency Compatibility​

Releases of Flowable Design, Work and Engage use versions of the open source Flowable dependencies that have not yet been published publicly on the Maven Central repository. These 'bugfix releases' can be retrieved by customers using the customer Flowable Maven repository credentials.

These versions contain fixes and have been QA'ed with the 2025.1.01 release. It's advised to upgrade your open source dependencies to the 'compatible' version mentioned below (and mentioned in the subsequent Service Packs section)

Open source dependency version: 7.3.0.16

Service Packs​

2025.1.02​

  • Added support for using Microsoft Entra ID as an IDM. See https://documentation.flowable.com/latest/admin/installs/platform-full#microsoft-entra-id for information on how to configure it
  • Exposed Model Usage as an Action in the Editor Toolbars
  • Improved the evaluation of backend expressions using the data dictionary
  • Improved syntax highlighting in global search
  • Increased the size of the script window in Flowable Design
  • Added support for making the script window full screen in Flowable Design
  • Added support for using reply to, forward to and multi select for Media Messages
  • Fixed issue with task indexing for tasks with a process instance reference, but where no process instance data is available.
  • Fixed issue when using flw.base64.encodeToString with content items
  • Fixed issue with AI Activated suggestion actions in Multi Tenant environments
  • Fixed issue with buttons in Themes management not being fully visible
  • Fixed issue with task list redirect in standalone app view
  • Fixed issue with flw.min not treating 0 as possible value
  • Fixed issue with html display breaking layout with long text
  • Fixed issue with Data Table select filter having hidden options
  • Fixed issue with error message for app revision when revision has space in key
  • Fixed issue with expose task to object not exporting scope id properly
  • Fixed issue with condition builder label for empty variable value
  • Fixed issue delete shortcut removing an element from the BPMN / CMMN canvas when a wizard is open
  • Fixed issue with missing button icons in exported forms
  • Fixed issue in Flowable Control not showing Message details in a Conversation
  • Fixed issue with Agent Instances not showing tenantId in Flowable Control
  • Upgraded Spring Boot to 3.5.4

Open source dependency version: 7.3.0.16