What is the extent of Flowable’s support of DMN -
1- Upon looking at the docs (over the last few weeks), my understanding is that there is strong support for decision tables themselves, including inputs/outputs/annotations as well as hit policies to work out which rules did pass and which did not.
2- There is support for JUEL but not for FEEL.
3- There is no support (yet) for chaining decisions (DRG?), though presumably we can use a DecisionTask and BPMN to chain multiple decisions together. I’m not quite aware of the difference here - is it mainly that the hit policies don’t run quite the same (e.g. would only run on the first decision table)?
Is there anything I should be aware of in terms of flowable and DMN?
Does anyone have any performance metrics of flowable’s DMN decision tables? e.g. is it more performant to run one big table of rules or several tables of smaller rules? Say I had a list of products to sell, would iterating over the new entire product catalogue with each product having its own decision table be performant? (talking a few hundred products with say 20/30 rules in each decision table)
Thanks - any pointers in terms of best practices would be great.