The current decision structures support only a fully automated mode of processing, whereby the criteria for advancing down any branch within a group is fully defined in the definition, and assumed to be followed at runtime.
However, 3 levels of processing are needed: fully automated (i.e. what is already there), 'decision support', where the defined conditions are understood as recommendations that can be overridden by the user at execution time, and 'ad hoc;', where multiple choices are defined whose criteria / justification are only provided at execution time by the performer.
Whoops, adhoc_group.members has wrong field description (“Set of Tasks to perform.”).
This is now corrected; it’s retrospectively added to Release-1.5.0 on the Release-1.5.0. I missed typing in the CR name in the first commit (grr) but here’s the first Git-diff; here’s the second; Also the direct content location (just look for ‘members’).