Generating Customized Decision Types and Codes

The developer must communicate with the rule author what the customized decision types and codes are. This communication can be as simple as a three column table where the first column lists the decision types, the second column lists the associated decision codes, and the third column describes the semantics of the pair. Falcon does not require you to associate a decision code with a decision type. Falcon, however, does not permit creating a decision code without a decision type.

Falcon reserves for customer use all decision types and decision types will be prefixed with custom. For example, if the decision type is defined as blockCode for the SendCustomAdvice function, then the name of the decision type is customblockCode. Custom decision types and codes must each be 32 bytes or less.

The associated function, DecisionExists() returns whether a specific decision exists for a specified decision type.