In IDIOM, a decision is always exactly one value that is the outcome produced by a formula, which is in turn a bounded collection of business rules. The formula operates on and for a single business context. The value produced by the formula is then handled by the decision that is executing it – the decision usually places the value into the decision’s own context node. At runtime, external applications access these decision outcomes by calling the IDIOM decision service and then reading the returned XML values (see IDIOM Architecture).
The repository of business rules is developed in IDIOM by decision designers, who create the decisions and formulas. These decisions and formulas are closely integrated with the decision requests the external application sends to the IDIOM rules repository at runtime.
In this section, we outline the processes that decision designers follow when developing and verifying decisions. The usual workflow is as follows:
•Create decision groups and decisions (see Creating decisions/groups). |
•Link decisions/decision groups to nodes on the schema – if needed (Linking decisions to a schema node). |
•Attach formulas to the decisions (see formulas and decisions). |
•Specify the order for runtime processing of the decisions/decision groups - if needed (see Ordering decisions for runtime processing). |
•Test decision execution (see Conducting an in-line test). |
NOTE: In some circumstances there will be a need for decisions that do not write their output to their context node. These decisions have a non-standard ‘control’ datatype and are known as control decisions. They are shown in light red in the decision model (see Menu Items information on changing decision datatypes, and Output nodes for information on how to create a schema that contains control decisions. Control decisions exist to control the processing flow through the decision model and do not write data values to any schema nodes. It follows that the formulas used by the Control decisions also do not generate output values – their results are directed to the IDIOM Decision Engine itself.