Running business rules on the Flowable DMN engine: hit policies, calling decisions from processes and cases, deployment and versioning, testing and decision history.
Picking the right hit policy for a Flowable decision table: FIRST, UNIQUE, ANY and PRIORITY for single results, OUTPUT ORDER, RULE ORDER and COLLECT for lists, strict mode behavior, and the rule overlaps each one tolerates.
Evaluating decision tables inside Flowable processes with the business rule task: mapping process variables to inputs, using results in gateways, and versioning rules separately from the process.
Using decision tasks in Flowable CMMN cases to route work, activate stages or set case variables from rules, and keeping case logic readable when many decisions are involved.
Calling the Flowable DMN engine as a decision service over REST: executing decisions by key, passing input variables, reading results, deployment endpoints, and securing access for other applications.
Releasing rule changes in Flowable without redeploying processes: decision definition keys and versions, one decision per file, tenant-specific decisions, and which version a running process picks up.
Testing Flowable decision tables before release: unit tests with deployed DMN files, test cases per rule and hit policy, regression suites for rule changes, and review steps with business owners.
Recording which rules fired in Flowable: DMN execution history for audit and troubleshooting, the Flowable 8 option to disable DMN history persistence, and the storage trade-off for high-volume decisions.
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.