Support for the "COLLECT" hit policy. #267

danfunk · 2022-11-21T20:25:57Z

DecisionTable constructor now expects a third argument (the HitPolicy)
DMNParser now checks for a hitPolicy attribute, but defaults ot "UNIQUE" as Camunda doesn't put another in there if Unique is selected.
DecisionTable deserializer will default to a hitPolicy of "UNIQUE" if not value is in the Json.
DMNEngine.decide() always returns an array of matched rules now.
DMNEngine.result() is a new method that returns the result (a dict to be added to the task.data) of running a decision table. * DecisionRunner (used in 100's of tests) makes the assumption that only one rule will match in it's "decide" function, but it has also has a new function called "result" which will give you the dict that is created when running a decision.
Moved logic out of the BusinessRuleTask so we aren't directly dealing with decisions and rules there, we deal with them in the DMNEngine.

* DecisionTable constructor now expects a third argument (the HitPolicy) * DMNParser now checks for a hitPolicy attribute, but defaults ot "UNIQUE" as Camunda doesn't put another in there if Unique is selected. * DecisionTable deserializer will default to a hitPolicy of "UNIQUE" if not value is in the Json. * DMNEngine.decide() always returns an array of matches rules now. * DMNEngine.result() is a new method that returns the result of running a decision table. Which feels cleaner to me. * DecisionRunner (used in 100's of tests) makes the assumption that only one rule will match in it's "decide" function, but it has anew function now called "result" which will give you the dict that is created when running a decision -- much cleaner I think. * Moved logic out of the BusinessRuleTask so we aren't directly dealing with decisions and rules there, we deal with them in the DMNEngine.