Decision tables
Define inputs, outputs, rules and supported hit policies in a form that can be read and reviewed.
Decision management
Take important rules out of code and meeting notes
When a rule affects who is eligible, where work is routed or when something must be escalated, people should be able to see it. Pūnaha keeps decision logic separate from the process or case that uses it, so the rule can be reviewed on its own.
Known inputs
Reviewable rules
Recorded result
Why separate decisions
A routing rule is not the same thing as a workflow
Imagine a service request that must be routed by value, risk and location. The process explains what happens before and after the routing point. The decision explains how those three inputs produce a destination.
Keeping the rule separate makes change easier to discuss. A policy owner can review the logic without tracing an entire process diagram, and the same decision can be used from more than one process or case.
A decision in practice
From a question to a result people can inspect
- 1
Name the question
Be clear about the result the decision is expected to return.
- 2
Define the inputs
Specify the information the rule needs and what happens when it is missing.
- 3
Write the rules
Use supported conditions or a decision table instead of scattering the logic across code and routing paths.
- 4
Use the decision
Call it from a workflow, BPMN-based process or CMMN-based case with mapped inputs and outputs.
- 5
Keep the result
Retain the output with the surrounding execution or case state that used it.
What Pūnaha provides
Decision logic that can take part in real work
Workflow decisions
Use conditions and business-rule modules inside a controlled workflow version.
BPMN business-rule tasks
Pass process data into decision logic and return the result to the running process.
CMMN decision tasks
Use a decision from a case and map the output back to case information or subsequent work.
Execution context
Keep the result with the run or case in which it was used.
Human review
Follow a decision with approval when policy, consequence or professional judgement requires a person.
Working with DMN files
Review the model before it becomes operational
Pūnaha can preview supported DMN XML, create or update an editable draft, and export supported decision logic as DMN.
The import preview shows what Pūnaha recognised and what needs attention before anything is created. A supported simple decision can become an editable module.
Imported decision tables can be retained for review, but we do not claim that every table from every DMN product will execute natively. The model, mappings and target workflow need to be checked before publication.
Preview
See the source format and conversion outcome before changing a draft.
Retain
Keep supported decision detail and source metadata with the editable model.
Map
Connect external references to approved resources in the environment where the decision will run.
Where the decision fits
Let each model answer its own question
| Model | The question | Example |
|---|---|---|
| DMN-aware decision | What result follows from these inputs and rules? | Eligibility, routing or escalation |
| BPMN-based process | What work happens, in what order and in response to which events? | Onboarding or fulfilment |
| CMMN-based case | What work is appropriate now that the situation has changed? | Investigation or incident response |
DMN support
What the current support does and does not mean
Pūnaha has automated coverage for its supported decision and interchange behaviour.
That supports the capabilities described here. It does not mean that an arbitrary external DMN model can be imported and executed without review.
We do not claim formal DMN conformance, certification or complete interoperability with every decision-modelling product.
Available now
Supported decision tables, conditions, workflow integration, preview, import mapping and export.
Checked internally
Automated tests for the decision behaviour and interchange paths Pūnaha controls.
Not claimed
Formal conformance or universal execution of imported DMN models.
Questions about DMN and decisions
Can Pūnaha import a DMN file?
Yes, within the supported model scope. Pūnaha previews the file and reports blocking or review outcomes before creating or updating a draft.
Can Pūnaha export decisions as DMN?
Yes. Supported conditions and decision logic can be exported as a DMN document. Pūnaha-specific information is retained as extensions where applicable.
Can a process or case call a decision?
Yes. A BPMN-based process can use a business-rule task, and a CMMN-based case can use a decision task with mapped inputs and outputs.
Will every imported DMN table run without changes?
No. The imported model must be reviewed against the currently supported execution scope and mapped to the target environment.
Is Pūnaha formally DMN conformant?
No. No formal DMN conformance or certification claim is made on this site.
Bring the rule everyone understands differently
We can turn it into defined inputs, visible logic and a result that fits clearly into the surrounding process or case.