Flowable engine capabilities that change how process applications are governed in production: moving running instances between versions, decision tables, and history retention.
Moving in-flight process instances to a new process definition version in Flowable: validating a migration first, activity mappings when task IDs change, batch migration, history handling, and release practices that avoid long-lived instances on old versions.
Moving business rules out of code into Flowable DMN decision tables: the DMN standard, hit policies, calling decisions from BPMN and CMMN, versioning and deploying rules, and testing tables before release.
Choosing what Flowable records and for how long: none, activity, audit and full history levels, form submissions linked to the authenticated user, querying history for evidence, and automatic history cleaning schedules that keep tables manageable.
Serving several organizations or business units from one Flowable engine: tenant IDs on deployments, instances, tasks and jobs, per-tenant versioning, tenant-aware queries, and the access checks your application must add because the engine does not enforce them.
Storing references to JPA entities in Flowable process variables instead of copying data: how the engine loads entities, querying processes by entity, transaction alignment with Spring, and when plain variables are safer.
Making Flowable timers and due dates respect working hours and holidays: default and custom business calendars, referencing a calendar from timer events, and testing SLA deadlines before go-live.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.