Hi,
Im trying to use a hierarchical DMN (DRD) where a child decision output informs a parent decision input. Whilst this pattern previously worked in platform 7, I get an incident in platform 8 indicating the parent decision table cannot find a variable corresponding to the child’s output.
Is this a bug, or am I missing how to link tables in a DRD? Ive attached a minimlast DMN and driver process to demonstrate… Just start the driver process with { “childInput” : true} as the payload…
ParentChild.dmn (3.0 KB)
ParentChildDaaS.bpmn (5.3 KB)
Hi Rob
Thank you for raising this up!
DMN in Camunda Platform 8 (C8) works a bit differently from Camunda Platform 7, especially when using DRG/DRD.
In your example, the required decision (i.e. child decision) has the id “DetermineChildDecision”. It has one output with the output name “childOutput”.
In the dependent decision (i.e. parent decision), it tries to access the result under the name “childOutput” (i.e. the name of the output).
In C8, the result is stored under the decision id instead of the output name. Try to fix the decision by changing the input expression to “DetermineChildDecision”.
Please have a look at the docs about required decisions:
Does this help you?
Best regards,
Philipp
1 Like
Thanks Philipp,
I had not realised how different the platform 8 DMN implementation was from platform 7…
regards
Rob