Released August 21, 2026
\nOpen source dependency version: 8.1.0.23
\n\n", "url": "https://documentation.flowable.com/latest/admin/release-notes/2026.1.0-release#202612", "title": "Flowable 2026.1.2", "summary": "Released August 21, 2026
\nOpen source dependency version: 8.1.0.23
\n\n", "date_modified": "2026-08-21T00:00:00.000Z", "tags": [ "2026.1", "service-pack" ] }, { "id": "https://documentation.flowable.com/latest/admin/release-notes/2025.2.01-release#2025209", "content_html": "Released August 21, 2026
\nOpen source dependency version: 8.0.0.20
\n\n", "url": "https://documentation.flowable.com/latest/admin/release-notes/2025.2.01-release#2025209", "title": "Flowable 2025.2.09", "summary": "Released August 21, 2026
\nOpen source dependency version: 8.0.0.20
\n\n", "date_modified": "2026-08-21T00:00:00.000Z", "tags": [ "2025.2", "service-pack" ] }, { "id": "https://documentation.flowable.com/latest/admin/release-notes/2026.1.0-release#202611", "content_html": "Released July 29, 2026
\nOpen source dependency version: 8.1.0.22
\n\n", "url": "https://documentation.flowable.com/latest/admin/release-notes/2026.1.0-release#202611", "title": "Flowable 2026.1.1", "summary": "Released July 29, 2026
\nOpen source dependency version: 8.1.0.22
\n\n", "date_modified": "2026-07-29T00:00:00.000Z", "tags": [ "2026.1", "service-pack" ] }, { "id": "https://documentation.flowable.com/latest/admin/release-notes/2025.2.01-release#2025208", "content_html": "Released July 29, 2026
\nOpen source dependency version: 8.0.0.20
\n\n", "url": "https://documentation.flowable.com/latest/admin/release-notes/2025.2.01-release#2025208", "title": "Flowable 2025.2.08", "summary": "Released July 29, 2026
\nOpen source dependency version: 8.0.0.20
\n\n", "date_modified": "2026-07-29T00:00:00.000Z", "tags": [ "2025.2", "service-pack" ] }, { "id": "https://documentation.flowable.com/latest/admin/release-notes/2026.1.0-release", "content_html": "<YoutubeVideo video="2sGqKRteEPM" />
\nFlowable Hub replaces Flowable Control — This version introduces Flowable Hub as new and updated version of Flowable Control using the same React frontend technology as the Design and Work UI.\nIn this release also Control is still provided, but starting with 2026.2, only Flowable Hub will be provided and Control will not be included anymore. For more information on the deprecation of Flowable Control please refer to the Flowable Control section.
\nUpdated versioning pattern — We updated the minor version to single digit, so instead of 2026.1.01 we now have 2026.1.1. The first version of the 2026.1 major version is 2026.1.0.
\nA new guardrailing feature has been added to be able to define rules and verifications of an agent request or response, allowing to trigger your business logic when one of these guardrails fails.
Added MCP support to be able to interact with the platform from an agentic application. There is support to for example start case or process instances, or get the current state of a process, or complete a task etc.
In the attachment form component a new option has been added to do document analysis when uploading the document. A document agent can be configured for it to do classification for a content model type and to extract metadata information. The extracted metadata can be used to fill a configured set of form fields, all with approval of the knowledge worker / user of the form.
When an email is received via the email inbound channel, the email content and its attachments can be automatically classified with a document agent to define the content model type. The email content and each attachment are classified separately.
Added a new agent evaluator feature that can be defined on utility, external and a2a agents. Evaluators are run asynchronously on the response of an agent call and can be used to review and evaluate the response values against expected values and a range of values.
The dashboard builder has been extended with agentic dashboard components to show number of agent executions, token information etc.
Added support for the OpenAI Responses API, including Codex models, and integrated built-in tools like web and file search.
Added support for using Data Dictionary and Data Objects as JSON input and output for agent models.
WCAG 2.2 AA compliance has been tested and audited and an audit report is available via your CSM or account manager.
Added support for document / content item events in Case and process models. A document event listener can be configured to listen to specific actions on documents in a specific folder, like creating a new document, update an existing document, setting a content model on a document, updating the metadata of a document etc. The document event information can be used to define case and process model logic, like starting a review and approve process when a new document is created.
Improved support for email inbound channels to store the email and attachment information as content items, so that they are automatically attached to a case or process instances and the email content and attachments can be used in the case model and process model logic.
Added out-of-the-box support for File, (S)FTP, SQL and Azure Service Bus channel types. This can be extended with additional Camel connector support because the Design side is extensible.
Introduce CMMN error handling, similar to the already existing BPMN error handling. This is for example used by the new guardrailing feature in the agentic case platform, when a business error is thrown when a guardrail is matched. BPMN errors now can bubble up to a root CMMN case and can be handled there if needed.
Added mocking capabilities to REST service registry models, which, when enabled, will be used as mock responses instead of calling the real service for the service registry call.
Added support for multipart/form-data for service registry calls to allow to use content items as input for a REST call.
A new expression has been added for content items with ${contentItem.metadata.myKey} and ${contentItem.definition.key} support. You can now easily access the metadata of a content item and the content model definition information.
Introduced a housekeeping option for provisional content items that are not attached to a case, process, task or other scope. These are mainly content items that were uploaded in a form, but not completed as part of the scope. This can be enabled with the flowable.content.provisional.enable-cleaning application property.
Improved case migration support to allow for task properties like form key, due date and candidate groups to be updated in the migration.
Improved the reindexing functionality to use the batch feature and jobs to perform the reindexing.
Added support for Lambda expression in functions. e.g. flw.array.filter(people, p -> p.age >= 18 && p.active == true)
Added new expressions for manipulating arrays and objects with flw.array and flw.data.
Added support for using Data Dictionary and Data Objects as JSON input and output for services models.
Added expression support for variable extractors. Note that this has a potential performance impact and should be carefully evaluated.
<YoutubeVideo video="2sGqKRteEPM" />
\nFlowable Hub replaces Flowable Control — This version introduces Flowable Hub as new and updated version of Flowable Control using the same React frontend technology as the Design and Work UI.\nIn this release also Control is still provided, but starting with 2026.2, only Flowable Hub will be provided and Control will not be included anymore. For more information on the deprecation of Flowable Control please refer to the Flowable Control section.
\nUpdated versioning pattern — We updated the minor version to single digit, so instead of 2026.1.01 we now have 2026.1.1. The first version of the 2026.1 major version is 2026.1.0.
\nA new guardrailing feature has been added to be able to define rules and verifications of an agent request or response, allowing to trigger your business logic when one of these guardrails fails.
Added MCP support to be able to interact with the platform from an agentic application. There is support to for example start case or process instances, or get the current state of a process, or complete a task etc.
In the attachment form component a new option has been added to do document analysis when uploading the document. A document agent can be configured for it to do classification for a content model type and to extract metadata information. The extracted metadata can be used to fill a configured set of form fields, all with approval of the knowledge worker / user of the form.
When an email is received via the email inbound channel, the email content and its attachments can be automatically classified with a document agent to define the content model type. The email content and each attachment are classified separately.
Added a new agent evaluator feature that can be defined on utility, external and a2a agents. Evaluators are run asynchronously on the response of an agent call and can be used to review and evaluate the response values against expected values and a range of values.
The dashboard builder has been extended with agentic dashboard components to show number of agent executions, token information etc.
Added support for the OpenAI Responses API, including Codex models, and integrated built-in tools like web and file search.
Added support for using Data Dictionary and Data Objects as JSON input and output for agent models.
WCAG 2.2 AA compliance has been tested and audited and an audit report is available via your CSM or account manager.
Added support for document / content item events in Case and process models. A document event listener can be configured to listen to specific actions on documents in a specific folder, like creating a new document, update an existing document, setting a content model on a document, updating the metadata of a document etc. The document event information can be used to define case and process model logic, like starting a review and approve process when a new document is created.
Improved support for email inbound channels to store the email and attachment information as content items, so that they are automatically attached to a case or process instances and the email content and attachments can be used in the case model and process model logic.
Added out-of-the-box support for File, (S)FTP, SQL and Azure Service Bus channel types. This can be extended with additional Camel connector support because the Design side is extensible.
Introduce CMMN error handling, similar to the already existing BPMN error handling. This is for example used by the new guardrailing feature in the agentic case platform, when a business error is thrown when a guardrail is matched. BPMN errors now can bubble up to a root CMMN case and can be handled there if needed.
Added mocking capabilities to REST service registry models, which, when enabled, will be used as mock responses instead of calling the real service for the service registry call.
Added support for multipart/form-data for service registry calls to allow to use content items as input for a REST call.
A new expression has been added for content items with ${contentItem.metadata.myKey} and ${contentItem.definition.key} support. You can now easily access the metadata of a content item and the content model definition information.
Introduced a housekeeping option for provisional content items that are not attached to a case, process, task or other scope. These are mainly content items that were uploaded in a form, but not completed as part of the scope. This can be enabled with the flowable.content.provisional.enable-cleaning application property.
Improved case migration support to allow for task properties like form key, due date and candidate groups to be updated in the migration.
Improved the reindexing functionality to use the batch feature and jobs to perform the reindexing.
Added support for Lambda expression in functions. e.g. flw.array.filter(people, p -> p.age >= 18 && p.active == true)
Added new expressions for manipulating arrays and objects with flw.array and flw.data.
Added support for using Data Dictionary and Data Objects as JSON input and output for services models.
Added expression support for variable extractors. Note that this has a potential performance impact and should be carefully evaluated.
Released June 17, 2026
\n<p> tags, aligning with previous versions.Open source dependency version: 8.0.0.19
\n\n", "url": "https://documentation.flowable.com/latest/admin/release-notes/2025.2.01-release#2025207", "title": "Flowable 2025.2.07", "summary": "Released June 17, 2026
\n<p> tags, aligning with previous versions.Open source dependency version: 8.0.0.19
\n\n", "date_modified": "2026-06-17T00:00:00.000Z", "tags": [ "2025.2", "service-pack" ] }, { "id": "https://documentation.flowable.com/latest/admin/release-notes/2025.1.01-release#2025113", "content_html": "Released June 17, 2026
\n<p> tags, aligning with previous versions.Open source dependency version: 7.3.0.32
\n\n", "url": "https://documentation.flowable.com/latest/admin/release-notes/2025.1.01-release#2025113", "title": "Flowable 2025.1.13", "summary": "Released June 17, 2026
\n<p> tags, aligning with previous versions.Open source dependency version: 7.3.0.32
\n\n", "date_modified": "2026-06-17T00:00:00.000Z", "tags": [ "2025.1", "service-pack" ] }, { "id": "https://documentation.flowable.com/latest/admin/release-notes/3.17.0-release#31717", "content_html": "Released June 17, 2026
\nFixed a migration issue that caused a NullPointerException when changing the process history level from 'none' to 'default' during an active migration.
Addressed an issue in legacy DataTable components where the space bar was ignored in filter input fields.
Introduced a customization option allowing users to create and use their own PDF viewer component instead of the default browser PDF viewer.
Fixed an issue where the default attribute on inclusive gateways was dropped during BPMN import in Flowable Design.
Resolved an issue in Flowable Design where migrating custom form components could fail due to incorrect handling of model relations.
Fixed a discrepancy in model version retrieval between model hierarchy and definition panels in Flowable Control, ensuring consistent version display.
Fixed the cursor behaviour in the conversation composer to maintain its position after an emoji is inserted, preventing it from jumping to the beginning of the line.
Updated Axios to version 1.16.1 to address a security vulnerability.
Upgraded Spring Boot to version 3.5.15.
\nOpen source dependency version: 7.2.0.26
Released June 17, 2026
\nFixed a migration issue that caused a NullPointerException when changing the process history level from 'none' to 'default' during an active migration.
Addressed an issue in legacy DataTable components where the space bar was ignored in filter input fields.
Introduced a customization option allowing users to create and use their own PDF viewer component instead of the default browser PDF viewer.
Fixed an issue where the default attribute on inclusive gateways was dropped during BPMN import in Flowable Design.
Resolved an issue in Flowable Design where migrating custom form components could fail due to incorrect handling of model relations.
Fixed a discrepancy in model version retrieval between model hierarchy and definition panels in Flowable Control, ensuring consistent version display.
Fixed the cursor behaviour in the conversation composer to maintain its position after an emoji is inserted, preventing it from jumping to the beginning of the line.
Updated Axios to version 1.16.1 to address a security vulnerability.
Upgraded Spring Boot to version 3.5.15.
\nOpen source dependency version: 7.2.0.26
Released May 13, 2026
\nOpen source dependency version: 8.0.0.18
\n\n", "url": "https://documentation.flowable.com/latest/admin/release-notes/2025.2.01-release#2025206", "title": "Flowable 2025.2.06", "summary": "Released May 13, 2026
\nOpen source dependency version: 8.0.0.18
\n\n", "date_modified": "2026-05-13T00:00:00.000Z", "tags": [ "2025.2", "service-pack" ] }, { "id": "https://documentation.flowable.com/latest/admin/release-notes/2025.1.01-release#2025112", "content_html": "Released May 13, 2026
\nOpen source dependency version: 7.3.0.31
\n\n", "url": "https://documentation.flowable.com/latest/admin/release-notes/2025.1.01-release#2025112", "title": "Flowable 2025.1.12", "summary": "Released May 13, 2026
\nOpen source dependency version: 7.3.0.31
\n\n", "date_modified": "2026-05-13T00:00:00.000Z", "tags": [ "2025.1", "service-pack" ] }, { "id": "https://documentation.flowable.com/latest/admin/release-notes/2025.2.01-release#2025205", "content_html": "Released April 16, 2026
\nReleased April 16, 2026
\nReleased April 16, 2026
\nOpen source dependency version: 7.3.0.30
\n\n", "url": "https://documentation.flowable.com/latest/admin/release-notes/2025.1.01-release#2025111", "title": "Flowable 2025.1.11", "summary": "Released April 16, 2026
\nOpen source dependency version: 7.3.0.30
\n\n", "date_modified": "2026-04-16T00:00:00.000Z", "tags": [ "2025.1", "service-pack" ] }, { "id": "https://documentation.flowable.com/latest/admin/release-notes/3.17.0-release#31716", "content_html": "Released April 16, 2026
\nOpen source dependency version: 7.2.0.25
\n\n", "url": "https://documentation.flowable.com/latest/admin/release-notes/3.17.0-release#31716", "title": "Flowable 3.17.16", "summary": "Released April 16, 2026
\nOpen source dependency version: 7.2.0.25
\n\n", "date_modified": "2026-04-16T00:00:00.000Z", "tags": [ "3.17", "service-pack" ] }, { "id": "https://documentation.flowable.com/latest/admin/release-notes/3.17.0-release#31715", "content_html": "Released March 24, 2026
\n<dependencyManagement>\n <dependencies>\n\n <dependency>\n <groupId>org.springframework.boot</groupId>\n <artifactId>spring-boot-dependencies</artifactId>\n <!-- keep this version in sync with the version of your parent pom -->\n <version>3.5.12</version>\n <type>pom</type>\n <scope>import</scope>\n </dependency>\n\n <!-- other entries here... -->\n\n </dependencies>\n</dependencyManagement>\nOpen source dependency version: 7.2.0.22
\n\n", "url": "https://documentation.flowable.com/latest/admin/release-notes/3.17.0-release#31715", "title": "Flowable 3.17.15", "summary": "Released March 24, 2026
\n<dependencyManagement>\n <dependencies>\n\n <dependency>\n <groupId>org.springframework.boot</groupId>\n <artifactId>spring-boot-dependencies</artifactId>\n <!-- keep this version in sync with the version of your parent pom -->\n <version>3.5.12</version>\n <type>pom</type>\n <scope>import</scope>\n </dependency>\n\n <!-- other entries here... -->\n\n </dependencies>\n</dependencyManagement>\nOpen source dependency version: 7.2.0.22
\n\n", "date_modified": "2026-03-24T00:00:00.000Z", "tags": [ "3.17", "service-pack" ] }, { "id": "https://documentation.flowable.com/latest/admin/release-notes/2025.2.01-release#2025204", "content_html": "Released March 19, 2026
\nOpen source dependency version: 8.0.0.13
\n\n", "url": "https://documentation.flowable.com/latest/admin/release-notes/2025.2.01-release#2025204", "title": "Flowable 2025.2.04", "summary": "Released March 19, 2026
\nOpen source dependency version: 8.0.0.13
\n\n", "date_modified": "2026-03-19T00:00:00.000Z", "tags": [ "2025.2", "service-pack" ] }, { "id": "https://documentation.flowable.com/latest/admin/release-notes/2025.1.01-release#2025110", "content_html": "Released March 19, 2026
\nOpen source dependency version: 7.3.0.27
\n\n", "url": "https://documentation.flowable.com/latest/admin/release-notes/2025.1.01-release#2025110", "title": "Flowable 2025.1.10", "summary": "Released March 19, 2026
\nOpen source dependency version: 7.3.0.27
\n\n", "date_modified": "2026-03-19T00:00:00.000Z", "tags": [ "2025.1", "service-pack" ] }, { "id": "https://documentation.flowable.com/latest/admin/release-notes/2025.2.01-release#2025203", "content_html": "Released February 19, 2026
\nOpen source dependency version: 8.0.0.11
\n\n", "url": "https://documentation.flowable.com/latest/admin/release-notes/2025.2.01-release#2025203", "title": "Flowable 2025.2.03", "summary": "Released February 19, 2026
\nOpen source dependency version: 8.0.0.11
\n\n", "date_modified": "2026-02-19T00:00:00.000Z", "tags": [ "2025.2", "service-pack" ] }, { "id": "https://documentation.flowable.com/latest/admin/release-notes/2025.1.01-release#2025109", "content_html": "Released February 19, 2026
\nOpen source dependency version: 7.3.0.26
\n\n", "url": "https://documentation.flowable.com/latest/admin/release-notes/2025.1.01-release#2025109", "title": "Flowable 2025.1.09", "summary": "Released February 19, 2026
\nOpen source dependency version: 7.3.0.26
\n\n", "date_modified": "2026-02-19T00:00:00.000Z", "tags": [ "2025.1", "service-pack" ] }, { "id": "https://documentation.flowable.com/latest/admin/release-notes/2025.1.01-release#2025108", "content_html": "Released January 27, 2026
\nOpen source dependency version: 7.3.0.23
\n\n", "url": "https://documentation.flowable.com/latest/admin/release-notes/2025.1.01-release#2025108", "title": "Flowable 2025.1.08", "summary": "Released January 27, 2026
\nOpen source dependency version: 7.3.0.23
\n\n", "date_modified": "2026-01-27T00:00:00.000Z", "tags": [ "2025.1", "service-pack" ] }, { "id": "https://documentation.flowable.com/latest/admin/release-notes/3.17.0-release#31714", "content_html": "Released January 22, 2026
\nOpen source dependency version: 7.2.0.22
\n\n", "url": "https://documentation.flowable.com/latest/admin/release-notes/3.17.0-release#31714", "title": "Flowable 3.17.14", "summary": "Released January 22, 2026
\nOpen source dependency version: 7.2.0.22
\n\n", "date_modified": "2026-01-22T00:00:00.000Z", "tags": [ "3.17", "service-pack" ] }, { "id": "https://documentation.flowable.com/latest/admin/release-notes/2025.2.01-release#2025202", "content_html": "Released January 16, 2026
\nOpen source dependency version: 8.0.0.7
\n\n", "url": "https://documentation.flowable.com/latest/admin/release-notes/2025.2.01-release#2025202", "title": "Flowable 2025.2.02", "summary": "Released January 16, 2026
\nOpen source dependency version: 8.0.0.7
\n\n", "date_modified": "2026-01-16T00:00:00.000Z", "tags": [ "2025.2", "service-pack" ] }, { "id": "https://documentation.flowable.com/latest/admin/release-notes/2025.1.01-release#2025107", "content_html": "Released January 15, 2026
\nOpen source dependency version: 7.3.0.23
\n\n", "url": "https://documentation.flowable.com/latest/admin/release-notes/2025.1.01-release#2025107", "title": "Flowable 2025.1.07", "summary": "Released January 15, 2026
\nOpen source dependency version: 7.3.0.23
\n\n", "date_modified": "2026-01-15T00:00:00.000Z", "tags": [ "2025.1", "service-pack" ] }, { "id": "https://documentation.flowable.com/latest/admin/release-notes/2025.1.01-release#2025106", "content_html": "Released December 17, 2025
\nOpen source dependency version: 7.3.0.22
\n\n", "url": "https://documentation.flowable.com/latest/admin/release-notes/2025.1.01-release#2025106", "title": "Flowable 2025.1.06", "summary": "Released December 17, 2025
\nOpen source dependency version: 7.3.0.22
\n\n", "date_modified": "2025-12-17T00:00:00.000Z", "tags": [ "2025.1", "service-pack" ] }, { "id": "https://documentation.flowable.com/latest/admin/release-notes/3.17.0-release#31713", "content_html": "Released December 17, 2025
\nOpen source dependency version: 7.2.0.22
\n\n", "url": "https://documentation.flowable.com/latest/admin/release-notes/3.17.0-release#31713", "title": "Flowable 3.17.13", "summary": "Released December 17, 2025
\nOpen source dependency version: 7.2.0.22
\n\n", "date_modified": "2025-12-17T00:00:00.000Z", "tags": [ "3.17", "service-pack" ] }, { "id": "https://documentation.flowable.com/latest/admin/release-notes/2025.2.01-release", "content_html": "<YoutubeVideo video="vvdbX33mAYs" />
\nAdded support for AI chat to the process, case, decision, form, service, agent, event, channel, data dictionary, data object model editors to allow using prompts to add new elements and new properties, or bulk update properties in the model.
Added support for AI chat in the app overview to get information about the models in the app using prompts, like getting an overview where a specific variable is used, or get all variables used in the app etc.
Added support for external agents implementing the A2A specification.
Added support to define tools for a utility agent to allow a LLM to fetch information from a tool when needed. Tools can be services or agents and therefore can get information from a wide variety of options, including script logic, REST services, and other agents.
Added a timeline visualisation in Control to show the requests and responses of an agent instance, including LLM calls, tool calls etc. For each entry in the timeline a detailed view with the request and response message information is shown.
Added support to view the number of agent invocations for each agent definition, and to see the token count for each agent definition.
Added support to define custom external agents using the same palette approach as for cases and processes. The runtime logic for the external agent invocation can be implemented using the ExternalAgentInvoker interface.
Added polling support to see if an external agent is completed.
Improved non-transactional execution of an agent task to not block database transactions.
Introduce a new AI button form element that can be used to invoke an agent model from an (auto-execute) form button.
Added a new "Trigger intent evaluation" task to the CMMN palette, so that an intent evaluation can be modeled.
Expose the document classification operation of a document agent.
Configure content transformation of popular file format when passing them to a LLM.
Added support for using tenant and app variables in prompts in an agent model.
Added an AI instruction property to content models to describe the content model type for usage in AI classification and other AI content logic.
Added support to configure the secret value for AWS Bedrock in an external agent model.
Added support to remove agent instance data as part of the regular housekeeping logic of case and process instances.
Implemented a new design system for the default Work UI and improved navigation patterns. Note that this will only apply if previously the default theme was used. In case a custom theme is used, this will still be used by the Work UI,\nbut due to changes in the navigation patterns and component structure adaptations to the custom theme might be needed.
Improved the form custom component CLI and support in Design and Work for exporting and importing apps using custom form components, to support using always the lastest deployed version of a custom form component, and to support using\nthe custom component CLI from a CI/CD to always publish the latest state of a custom component project to a Work instance.
Added an Apache Camel channel option to inbound and outbound channel models to allow to use Camel routes for inbound or outbound events.\nSince Apache Camel uses different modules for different channel types, the Camel module dependencies of choice should be added to your Work application.\nAlso the Apache Camel Flowable module needs to be present.
Added support to automatically apply the database changes for a data object model on deployment. This can be configured on the data object changelog model.\nBecause making changes to the database schema can have implications, this feature needs to be explicitly enabled with the flowable.dataobject.auto-update-data-object-schema-definitions=true property.
Added support for using Microsoft Entra as an IDM. See the installation guide for information on how to configure it.
Added support to use a SLA model for a case or process, in addition to tasks.
Improved SLA reaction and completion time for the type day to use full working days instead of translating days to 24 hours. In case the old behaviour is still preferred the flowable.platform.enable-sla-legacy-working-day-behavior=true can be set.
Fixed issue with case migration with existing sentry part instances on a plan item instance that is terminated.
Fixed issue with using the change activity state API for multi instance tasks.
Fixed issue to support attachment fields in outcome forms.
Introduced new property flowable.http.client.spring-web-client.netty.max-header-size to set a custom max header size (default 8192 bytes) for HTTP and service registry task calls.
Introduced new properties flowable.http.client.apache5.max-connections (default 500) and flowable.http.client.apache5.max-connections-per-route (default 250) to be able to set a custom maximum amount of connections and a custom maximum amount\nof connections per route url for the HTTP and service registry task calls.
Improved support for a case or process starter that should not have permissions on the created instance by adding additional configuration options in the security policy model.
Added an option in the security policy model to exclude root and parent variables in case the user has no read permission on the root and/or parent instance.
Added option to execute a DMN decision without storing historic data.
Added autocomplete support for data object select form components.
Improved support to cancel a document upload while it is in progress.
Improved support for a view refresh for action buttons on a page.
<YoutubeVideo video="vvdbX33mAYs" />
\nAdded support for AI chat to the process, case, decision, form, service, agent, event, channel, data dictionary, data object model editors to allow using prompts to add new elements and new properties, or bulk update properties in the model.
Added support for AI chat in the app overview to get information about the models in the app using prompts, like getting an overview where a specific variable is used, or get all variables used in the app etc.
Added support for external agents implementing the A2A specification.
Added support to define tools for a utility agent to allow a LLM to fetch information from a tool when needed. Tools can be services or agents and therefore can get information from a wide variety of options, including script logic, REST services, and other agents.
Added a timeline visualisation in Control to show the requests and responses of an agent instance, including LLM calls, tool calls etc. For each entry in the timeline a detailed view with the request and response message information is shown.
Added support to view the number of agent invocations for each agent definition, and to see the token count for each agent definition.
Added support to define custom external agents using the same palette approach as for cases and processes. The runtime logic for the external agent invocation can be implemented using the ExternalAgentInvoker interface.
Added polling support to see if an external agent is completed.
Improved non-transactional execution of an agent task to not block database transactions.
Introduce a new AI button form element that can be used to invoke an agent model from an (auto-execute) form button.
Added a new "Trigger intent evaluation" task to the CMMN palette, so that an intent evaluation can be modeled.
Expose the document classification operation of a document agent.
Configure content transformation of popular file format when passing them to a LLM.
Added support for using tenant and app variables in prompts in an agent model.
Added an AI instruction property to content models to describe the content model type for usage in AI classification and other AI content logic.
Added support to configure the secret value for AWS Bedrock in an external agent model.
Added support to remove agent instance data as part of the regular housekeeping logic of case and process instances.
Implemented a new design system for the default Work UI and improved navigation patterns. Note that this will only apply if previously the default theme was used. In case a custom theme is used, this will still be used by the Work UI,\nbut due to changes in the navigation patterns and component structure adaptations to the custom theme might be needed.
Improved the form custom component CLI and support in Design and Work for exporting and importing apps using custom form components, to support using always the lastest deployed version of a custom form component, and to support using\nthe custom component CLI from a CI/CD to always publish the latest state of a custom component project to a Work instance.
Added an Apache Camel channel option to inbound and outbound channel models to allow to use Camel routes for inbound or outbound events.\nSince Apache Camel uses different modules for different channel types, the Camel module dependencies of choice should be added to your Work application.\nAlso the Apache Camel Flowable module needs to be present.
Added support to automatically apply the database changes for a data object model on deployment. This can be configured on the data object changelog model.\nBecause making changes to the database schema can have implications, this feature needs to be explicitly enabled with the flowable.dataobject.auto-update-data-object-schema-definitions=true property.
Added support for using Microsoft Entra as an IDM. See the installation guide for information on how to configure it.
Added support to use a SLA model for a case or process, in addition to tasks.
Improved SLA reaction and completion time for the type day to use full working days instead of translating days to 24 hours. In case the old behaviour is still preferred the flowable.platform.enable-sla-legacy-working-day-behavior=true can be set.
Fixed issue with case migration with existing sentry part instances on a plan item instance that is terminated.
Fixed issue with using the change activity state API for multi instance tasks.
Fixed issue to support attachment fields in outcome forms.
Introduced new property flowable.http.client.spring-web-client.netty.max-header-size to set a custom max header size (default 8192 bytes) for HTTP and service registry task calls.
Introduced new properties flowable.http.client.apache5.max-connections (default 500) and flowable.http.client.apache5.max-connections-per-route (default 250) to be able to set a custom maximum amount of connections and a custom maximum amount\nof connections per route url for the HTTP and service registry task calls.
Improved support for a case or process starter that should not have permissions on the created instance by adding additional configuration options in the security policy model.
Added an option in the security policy model to exclude root and parent variables in case the user has no read permission on the root and/or parent instance.
Added option to execute a DMN decision without storing historic data.
Added autocomplete support for data object select form components.
Improved support to cancel a document upload while it is in progress.
Improved support for a view refresh for action buttons on a page.
Released November 20, 2025
\nOpen source dependency version: 7.2.0.22
\n\n", "url": "https://documentation.flowable.com/latest/admin/release-notes/3.17.0-release#31712", "title": "Flowable 3.17.12", "summary": "Released November 20, 2025
\nOpen source dependency version: 7.2.0.22
\n\n", "date_modified": "2025-11-20T00:00:00.000Z", "tags": [ "3.17", "service-pack" ] }, { "id": "https://documentation.flowable.com/latest/admin/release-notes/2025.1.01-release#2025105", "content_html": "Released November 7, 2025
\nOpen source dependency version: 7.3.0.22
\n\n", "url": "https://documentation.flowable.com/latest/admin/release-notes/2025.1.01-release#2025105", "title": "Flowable 2025.1.05", "summary": "Released November 7, 2025
\nOpen source dependency version: 7.3.0.22
\n\n", "date_modified": "2025-11-07T00:00:00.000Z", "tags": [ "2025.1", "service-pack" ] }, { "id": "https://documentation.flowable.com/latest/admin/release-notes/2025.1.01-release#2025104", "content_html": "Released November 4, 2025
\nOpen source dependency version: 7.3.0.22
\n\n", "url": "https://documentation.flowable.com/latest/admin/release-notes/2025.1.01-release#2025104", "title": "Flowable 2025.1.04", "summary": "Released November 4, 2025
\nOpen source dependency version: 7.3.0.22
\n\n", "date_modified": "2025-11-04T00:00:00.000Z", "tags": [ "2025.1", "service-pack" ] }, { "id": "https://documentation.flowable.com/latest/admin/release-notes/3.17.0-release#31711", "content_html": "Released October 14, 2025
\nOpen source dependency version: 7.2.0.22
\n\n", "url": "https://documentation.flowable.com/latest/admin/release-notes/3.17.0-release#31711", "title": "Flowable 3.17.11", "summary": "Released October 14, 2025
\nOpen source dependency version: 7.2.0.22
\n\n", "date_modified": "2025-10-14T00:00:00.000Z", "tags": [ "3.17", "service-pack" ] }, { "id": "https://documentation.flowable.com/latest/admin/release-notes/3.17.0-release#31710", "content_html": "Released September 25, 2025
\nOpen source dependency version: 7.2.0.18
\n\n", "url": "https://documentation.flowable.com/latest/admin/release-notes/3.17.0-release#31710", "title": "Flowable 3.17.10", "summary": "Released September 25, 2025
\nOpen source dependency version: 7.2.0.18
\n\n", "date_modified": "2025-09-25T00:00:00.000Z", "tags": [ "3.17", "service-pack" ] }, { "id": "https://documentation.flowable.com/latest/admin/release-notes/2025.1.01-release#2025103", "content_html": "Released September 11, 2025
\nOpen source dependency version: 7.3.0.21
\n\n", "url": "https://documentation.flowable.com/latest/admin/release-notes/2025.1.01-release#2025103", "title": "Flowable 2025.1.03", "summary": "Released September 11, 2025
\nOpen source dependency version: 7.3.0.21
\n\n", "date_modified": "2025-09-11T00:00:00.000Z", "tags": [ "2025.1", "service-pack" ] }, { "id": "https://documentation.flowable.com/latest/admin/release-notes/3.17.0-release#3179", "content_html": "Released August 6, 2025
\nOpen source dependency version: 7.2.0.18
\n\n", "url": "https://documentation.flowable.com/latest/admin/release-notes/3.17.0-release#3179", "title": "Flowable 3.17.9", "summary": "Released August 6, 2025
\nOpen source dependency version: 7.2.0.18
\n\n", "date_modified": "2025-08-06T00:00:00.000Z", "tags": [ "3.17", "service-pack" ] }, { "id": "https://documentation.flowable.com/latest/admin/release-notes/2025.1.01-release#2025102", "content_html": "Released July 29, 2025
\nOpen source dependency version: 7.3.0.16
\n\n", "url": "https://documentation.flowable.com/latest/admin/release-notes/2025.1.01-release#2025102", "title": "Flowable 2025.1.02", "summary": "Released July 29, 2025
\nOpen source dependency version: 7.3.0.16
\n\n", "date_modified": "2025-07-29T00:00:00.000Z", "tags": [ "2025.1", "service-pack" ] }, { "id": "https://documentation.flowable.com/latest/admin/release-notes/3.17.0-release#3178", "content_html": "Released July 18, 2025
\nOpen source dependency version: 7.2.0.18
\n\n", "url": "https://documentation.flowable.com/latest/admin/release-notes/3.17.0-release#3178", "title": "Flowable 3.17.8", "summary": "Released July 18, 2025
\nOpen source dependency version: 7.2.0.18
\n\n", "date_modified": "2025-07-18T00:00:00.000Z", "tags": [ "3.17", "service-pack" ] }, { "id": "https://documentation.flowable.com/latest/admin/release-notes/2025.1.01-release", "content_html": "<YoutubeVideo video="CWgFqNnHciE" />
\nA new versioning pattern has been introduced with the major version now including the year of the release and the an incremental version identifier.\nWith 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.\nSo therefore the full version identifier is 2025.1.01 for this release and a new service pack will be 2025.1.02 and further.\nNote 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.\nAlso 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.\nMore information can be found in your Flowable support portal.
\nIntroduced 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.\nThe 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\nhave 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\nand 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\nthe agent exchange messages that are sent and received from the AI service interactions.
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.
<YoutubeVideo video="CWgFqNnHciE" />
\nA new versioning pattern has been introduced with the major version now including the year of the release and the an incremental version identifier.\nWith 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.\nSo therefore the full version identifier is 2025.1.01 for this release and a new service pack will be 2025.1.02 and further.\nNote 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.\nAlso 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.\nMore information can be found in your Flowable support portal.
\nIntroduced 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.\nThe 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\nhave 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\nand 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\nthe agent exchange messages that are sent and received from the AI service interactions.
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.
Released July 15, 2025
\nOpen source dependency version: 7.2.0.18
\n\n", "url": "https://documentation.flowable.com/latest/admin/release-notes/3.17.0-release#3177", "title": "Flowable 3.17.7", "summary": "Released July 15, 2025
\nOpen source dependency version: 7.2.0.18
\n\n", "date_modified": "2025-07-15T00:00:00.000Z", "tags": [ "3.17", "service-pack" ] }, { "id": "https://documentation.flowable.com/latest/admin/release-notes/3.17.0-release#3176", "content_html": "Released June 18, 2025
\ndependencyManagement section in your application's pom.xml and add the spring-boot-dependencies bom as following:\n <dependencyManagement>\n <dependencies>\n <dependency>\n <groupId>org.springframework.boot</groupId>\n <artifactId>spring-boot-dependencies</artifactId>\n <!-- keep this version in sync with the version of your parent pom -->\n <version>3.4.7</version>\n <type>pom</type>\n <scope>import</scope>\n </dependency>\n <!-- other entries here... -->\n </dependencies>\n </dependencyManagement>\nOpen source dependency version: 7.2.0.18
\n\n", "url": "https://documentation.flowable.com/latest/admin/release-notes/3.17.0-release#3176", "title": "Flowable 3.17.6", "summary": "Released June 18, 2025
\ndependencyManagement section in your application's pom.xml and add the spring-boot-dependencies bom as following:\n <dependencyManagement>\n <dependencies>\n <dependency>\n <groupId>org.springframework.boot</groupId>\n <artifactId>spring-boot-dependencies</artifactId>\n <!-- keep this version in sync with the version of your parent pom -->\n <version>3.4.7</version>\n <type>pom</type>\n <scope>import</scope>\n </dependency>\n <!-- other entries here... -->\n </dependencies>\n </dependencyManagement>\nOpen source dependency version: 7.2.0.18
\n\n", "date_modified": "2025-06-18T00:00:00.000Z", "tags": [ "3.17", "service-pack" ] }, { "id": "https://documentation.flowable.com/latest/admin/release-notes/3.17.0-release#3175", "content_html": "Released June 5, 2025
\nOpen source dependency version: 7.2.0.18
\n\n", "url": "https://documentation.flowable.com/latest/admin/release-notes/3.17.0-release#3175", "title": "Flowable 3.17.5", "summary": "Released June 5, 2025
\nOpen source dependency version: 7.2.0.18
\n\n", "date_modified": "2025-06-05T00:00:00.000Z", "tags": [ "3.17", "service-pack" ] }, { "id": "https://documentation.flowable.com/latest/admin/release-notes/3.17.0-release#3174", "content_html": "Released April 10, 2025
\nOpen source dependency version: 7.2.0.17
\n\n", "url": "https://documentation.flowable.com/latest/admin/release-notes/3.17.0-release#3174", "title": "Flowable 3.17.4", "summary": "Released April 10, 2025
\nOpen source dependency version: 7.2.0.17
\n\n", "date_modified": "2025-04-10T00:00:00.000Z", "tags": [ "3.17", "service-pack" ] }, { "id": "https://documentation.flowable.com/latest/admin/release-notes/3.17.0-release#3173", "content_html": "Released April 3, 2025
\nOpen source dependency version: 7.2.0.17
\n\n", "url": "https://documentation.flowable.com/latest/admin/release-notes/3.17.0-release#3173", "title": "Flowable 3.17.3", "summary": "Released April 3, 2025
\nOpen source dependency version: 7.2.0.17
\n\n", "date_modified": "2025-04-03T00:00:00.000Z", "tags": [ "3.17", "service-pack" ] }, { "id": "https://documentation.flowable.com/latest/admin/release-notes/3.17.0-release#3172", "content_html": "Released February 28, 2025
\nOpen source dependency version: 7.2.0.13
\n\n", "url": "https://documentation.flowable.com/latest/admin/release-notes/3.17.0-release#3172", "title": "Flowable 3.17.2", "summary": "Released February 28, 2025
\nOpen source dependency version: 7.2.0.13
\n\n", "date_modified": "2025-02-28T00:00:00.000Z", "tags": [ "3.17", "service-pack" ] }, { "id": "https://documentation.flowable.com/latest/admin/release-notes/3.17.0-release#3171", "content_html": "Released January 30, 2025
\nOpen source dependency version: 7.2.0.12
\n\n", "url": "https://documentation.flowable.com/latest/admin/release-notes/3.17.0-release#3171", "title": "Flowable 3.17.1", "summary": "Released January 30, 2025
\nOpen source dependency version: 7.2.0.12
\n\n", "date_modified": "2025-01-30T00:00:00.000Z", "tags": [ "3.17", "service-pack" ] }, { "id": "https://documentation.flowable.com/latest/admin/release-notes/3.17.0-release", "content_html": "<YoutubeVideo video="E-vsPYHRIx8" />
\nAdded support for the Intelligent Document Processing (IDP) integration with ABBYY. Content items that are available within Flowable can be sent to ABBYY for processing.\nThis is supported for automated processing, but also a manual task in ABBYY to do the document processing is supported.\nNote that the ABBYY feature require a specific ABBYY component to be enabled in the license file for which you can reach out to your CSM or Flowable Sales to discuss the contract terms.
Added new feature to orchestrate RPA agents of the RPA framework with Flowable. An RPA task can be added to your process model and input and output parameters can be defined.\nFor the agent the following external worker Python client is needed to execute the RPA logic RPA Python client.
Added a new incident reporting feature that shows the following incidents that can happen when running Flowable Work, saturation of the database connection pool and the task executor queue.\nAlso slow jobs, slow service executions and large ElasticSearch index requests are logged as an incident. The thresholds for when an incident is created can be configured\nusing application properties. It's recommended to check the incident reporting on regular basis to check for any issues with the application.
Improved the indexing to Elasticsearch for bigger hierarchies with a lot of performance improvements. Before this change, a big hierarchy of a root case instance\nwith several layers of process instances and tasks, could lead to a big Elasticsearch update of more than 10k entities.\nA lot of the logic is now loaded one time in memory to prevent 1-N queries from being performed, which improves to performance of the indexing dramatically.\nIn addition, to prevent too big JSON document updates to be sent to Elasticsearch, the indexing is done in batches.
Added support to return the total amount of items in the data object search API. For database data objects an additional query is done to return the total amount of items.\nFor REST data objects it's now possible to map a value from the search result in the REST response as the total amount value. This enables to allow for paging support with the data object REST API\nto be used in data tables for example.
The human task name, description, form key and category values are now updated for existing task instances when performing a case migration.
Improved the case migration to automatically terminate plan items that are not existing in the new case definition version, to simplify defining a case migration.
Improved the audit trail UI to allow for sorting and filtering on specific type and sub type values, and also show the payload for a specific item.
Improved the housekeeping logic to improve the queries that are performed to be more efficient and don't include for example sorting.
Added a new slider form field component that allows to show a number value on a scale.
Added support for a select and data table form field type that simplifies the usage of a service model request and response with these form field types.
Added support to copy and paste images into a rich text field in a form.
Added support to get master data instances from the default tenant.
Improved version handling with a data object instance, to ensure that newly deployed data object definition versions don't impact existing data object instances.
Improved support to provide translations for an app and page name.
Improved mail channel handling, Flowable now uses its own polling mechanism and processes one message at a time. The polling interval is used after no more messages have been received. IDLE support and max message per poll are no longer used.
Added support to export data for data object data tables.
Improved support for sorting and filtering columns in a data object data table.
Ensure that a search field for a data table doesn't trigger a refresh of the data while typing. A debounce period of 1 second is used for the triggering.
The case and process instance search API returns now also the assignee value.
Added support to skip a receive task, including the event registry tasks, based on a conditional expression.
Added support to put variable values in an asynchronous way on a case or process instance. In cases where variable updates can happen in parallel, this makes sure that variable updates will get performed in sequence.
Improved the user interaction for deleting an item in a multi sub form component.
The license export uses a md5 hash for the user id information now, to be able to match users better across different Flowable instances.
Updated the supported databases with the latest versions of Oracle, Microsoft SQL Server etc.
Removed the dependency on Liquibase for managing the Flowable Work database schema. Instead, a manual sql approach is used that was already used for the BPMN engine since the start of the Flowable project.\nThis has no direct impact for the usage and installation of Flowable Work.
<YoutubeVideo video="E-vsPYHRIx8" />
\nAdded support for the Intelligent Document Processing (IDP) integration with ABBYY. Content items that are available within Flowable can be sent to ABBYY for processing.\nThis is supported for automated processing, but also a manual task in ABBYY to do the document processing is supported.\nNote that the ABBYY feature require a specific ABBYY component to be enabled in the license file for which you can reach out to your CSM or Flowable Sales to discuss the contract terms.
Added new feature to orchestrate RPA agents of the RPA framework with Flowable. An RPA task can be added to your process model and input and output parameters can be defined.\nFor the agent the following external worker Python client is needed to execute the RPA logic RPA Python client.
Added a new incident reporting feature that shows the following incidents that can happen when running Flowable Work, saturation of the database connection pool and the task executor queue.\nAlso slow jobs, slow service executions and large ElasticSearch index requests are logged as an incident. The thresholds for when an incident is created can be configured\nusing application properties. It's recommended to check the incident reporting on regular basis to check for any issues with the application.
Improved the indexing to Elasticsearch for bigger hierarchies with a lot of performance improvements. Before this change, a big hierarchy of a root case instance\nwith several layers of process instances and tasks, could lead to a big Elasticsearch update of more than 10k entities.\nA lot of the logic is now loaded one time in memory to prevent 1-N queries from being performed, which improves to performance of the indexing dramatically.\nIn addition, to prevent too big JSON document updates to be sent to Elasticsearch, the indexing is done in batches.
Added support to return the total amount of items in the data object search API. For database data objects an additional query is done to return the total amount of items.\nFor REST data objects it's now possible to map a value from the search result in the REST response as the total amount value. This enables to allow for paging support with the data object REST API\nto be used in data tables for example.
The human task name, description, form key and category values are now updated for existing task instances when performing a case migration.
Improved the case migration to automatically terminate plan items that are not existing in the new case definition version, to simplify defining a case migration.
Improved the audit trail UI to allow for sorting and filtering on specific type and sub type values, and also show the payload for a specific item.
Improved the housekeeping logic to improve the queries that are performed to be more efficient and don't include for example sorting.
Added a new slider form field component that allows to show a number value on a scale.
Added support for a select and data table form field type that simplifies the usage of a service model request and response with these form field types.
Added support to copy and paste images into a rich text field in a form.
Added support to get master data instances from the default tenant.
Improved version handling with a data object instance, to ensure that newly deployed data object definition versions don't impact existing data object instances.
Improved support to provide translations for an app and page name.
Improved mail channel handling, Flowable now uses its own polling mechanism and processes one message at a time. The polling interval is used after no more messages have been received. IDLE support and max message per poll are no longer used.
Added support to export data for data object data tables.
Improved support for sorting and filtering columns in a data object data table.
Ensure that a search field for a data table doesn't trigger a refresh of the data while typing. A debounce period of 1 second is used for the triggering.
The case and process instance search API returns now also the assignee value.
Added support to skip a receive task, including the event registry tasks, based on a conditional expression.
Added support to put variable values in an asynchronous way on a case or process instance. In cases where variable updates can happen in parallel, this makes sure that variable updates will get performed in sequence.
Improved the user interaction for deleting an item in a multi sub form component.
The license export uses a md5 hash for the user id information now, to be able to match users better across different Flowable instances.
Updated the supported databases with the latest versions of Oracle, Microsoft SQL Server etc.
Removed the dependency on Liquibase for managing the Flowable Work database schema. Instead, a manual sql approach is used that was already used for the BPMN engine since the start of the Flowable project.\nThis has no direct impact for the usage and installation of Flowable Work.