{"full_name":"flowable/flowable-engine","owner":"flowable","name":"flowable-engine","shard":"1","url":"https://github.com/flowable/flowable-engine","description":"A compact and highly efficient workflow and Business Process Management (BPM) platform for developers, system admins and business users.","homepage":"https://www.flowable.org","topics":["bpmn","java","workflow","workflow-engine"],"tag_pages":["bpmn","java","workflow","workflow-engine"],"language":"Java","license":"Apache-2.0","avatar":"https://avatars.githubusercontent.com/u/22557067?v=4","created_at":"2016-10-13T07:21:43Z","pushed_at":"2026-11-13T15:08:07Z","metrics":{"stars":9657,"forks":2909,"watchers":265,"issues":1430,"prs":2892,"releases":29,"issues_open":385,"issues_closed":1045,"prs_open":68,"prs_closed":615,"prs_merged":2209,"discussions":0},"growth":{"day":{"stars":3,"forks":0,"base_day":"2026-11-15"}},"history":{"dates":["2026-11-10","2026-11-11","2026-11-12","2026-11-13","2026-11-14","2026-11-15","2026-11-16"],"stars":[9641,9646,9649,9650,9653,9654,9657],"forks":[2907,2906,2907,2907,2908,2909,2909],"watchers":[null,265,265,265,265,265,265],"issues_open":[null,384,384,384,384,384,385],"prs_open":[null,67,68,68,68,68,68]},"boards":{},"same_owner":[],"issues":[{"number":3944,"title":"How to return two multi-instance tasks","comments":25,"created_at":"2024-08-10T06:33:04Z"},{"number":1741,"title":"Different behaviour between parallel and inclusive gateways","comments":18,"created_at":"2019-05-13T07:46:57Z"},{"number":3683,"title":"Application run failed：Table \"ACT_RE_DEPLOYMENT\"","comments":14,"created_at":"2023-07-13T09:49:33Z"},{"number":2346,"title":"Flowable engine IntelliJ plugin","comments":14,"created_at":"2020-05-17T09:41:56Z"},{"number":3577,"title":"Bad behavior using Parallel Gateway with 2 end events","comments":12,"created_at":"2023-01-06T14:37:42Z"},{"number":3785,"title":"主业务项目有3个以上数据源集成时存的问题 Problems in integrating multiple data sources during project implementation","comments":10,"created_at":"2023-11-26T02:38:51Z"},{"number":3403,"title":"Flowable Timer Start Event not auto deleted when there is new deployment version ","comments":10,"created_at":"2022-07-25T12:11:15Z"},{"number":3294,"title":"flowable-6.7.2 Table 'workflow.flw_channel_definition' doesn't exis","comments":10,"created_at":"2022-05-03T17:14:18Z"}],"discussions":[],"latest_release":{"name":"Flowable 8.0.0 Release","tag":"flowable-8.0.0","published_at":"2026-02-27T16:35:48Z","body":"### Breaking Changes\r\n\r\n* **Upgrade to Spring Framework 7 and Spring Boot 4** - Flowable 8 is now based on Spring Framework 7 and Spring Boot 4. There is no support for Spring Boot 3 anymore.\r\n* **Upgrade to Jackson 3** - Jackson 3 is now the default JSON library. Jackson 2 is still supported via a compatibility layer\r\n* **Remove JUnit 3 and JUnit 4 support** - JUnit 3 and JUnit 4 testing support, deprecated in 7.2.0, has been removed. Use JUnit 5 (Jupiter) exclusively\r\n\r\n### New Features\r\n\r\n* **Lambda Expression support in expressions** - Lambda expressions are now supported in expressions. The `planItemInstances` keyword has been expanded to support filtering based on a predicate using lambda expressions\r\n* The method `stream()` can be used to obtain a `java.util.stream.Stream` from a collection. e.g. `${customers.stream().filter(customer -> customer.type eq 'premium').toList()}` to get a list of premium customers or `${customers.stream().map(customer -> customer.name).toList()` to get the names of all the customers.\r\n* The `planItemInstances` now expose a `filter(Predicate<DelegatePlanItemInstance> predicate)` method that can be used to provide custom filter options.\r\n* **Date variables with milliseconds** - Date variables will now include the milliseconds when they are returned over REST. E.g., up to now a date variable with the value of `2020-05-04T09:25:45.583Z` would have been returned as `2020-05-04T09:25:45Z`. However, now it would be returned as `2020-05-04T09:25:45.583Z` which is still ISO 8601 compliant.\r\n* **Date properties in UTC** - Date properties e.g., Process Instance start time will be returned as an ISO 8601 in the UTC timezone. E.g., if the start time was returned as `2025-09-24T09:58:12.609+02:00` now it is returned as `2025-09-24T07:58:12.609Z`.\r\n* **Access definition information in expressions during deployment** - Expressions can now access some of the definition information in expressions resolved during deployment. e.g. in Start Timer expression `${variableContainer.definitionKey}` to access the definition key\r\n* **Case and Process instance migration improvements**:\r\n  - Support for updating more task properties when doing case and process instance migration\r\n  - Case and process instance migration validation is now available in the REST API\r\n  - Option to automatically create plan item instances for new plan items during case instance migration\r\n* **End user tracking** - Added `endUserId` for historic process/case instances and `state` for historic process instances\r\n* **Case and Process end interceptor** - Added case and process end interceptor support\r\n* **Business status events** - Dispatch events when updating the business status of a case or process\r\n* **Event Registry hookpoints** - Added hookpoints to event registry for event payload types\r\n* **Possibility to disable DMN history persistence** - Added option to disable history persistence when executing DMN decisions\r\n* **Support Java Records in Expressions**\r\n\r\n### Performance Improvements\r\n\r\n* Improve Expression coercion performance\r\n* Long String variables now store a cached value, avoiding repeated deserialization\r\n* Reduce unnecessary `ObjectMapper` instance creation - reuse the one from engine configuration\r\n\r\n### Bug Fixes\r\n\r\n* Fix issue with multiple case reactivations with a parent case instance\r\n* Fix NPE when having two sentries, and one doesn't have an `ifPart`\r\n* Fix case / process instance ended invoked twice when undeploying deeply nested app\r\n* Fix issue with moving parallel multi-instance activities to a single activity\r\n* Ensure that multiple character events for the same element are handled correctly in XML parsing\r\n* Make sure that `BeanELResolver` and DMN Expression resolution propagates the exception cause\r\n* Avoid 'Invalid reference in diagram interchange definition' warning message in logs when plan items are part of a plan fragment\r\n* Unlock exclusive jobs when unacquiring all jobs of a worker\r\n* Unacquiring external w","is_prerelease":false},"readme":true,"readme_zh":false,"news":[],"stale":false,"snapshot_at":"2026-11-16T09:23:14Z","history_start":"2026-09-06"}