By attaching rule statements to the rule columns Corticon provides an automatic mechanism for providing an explanation of which rules fired and why. This makes generating an audit trail very easy

However the messages that are generated by this means are inaccessible to Corticon rules which means you cannot write rules to eliminate duplicate messages or determine the more important messages or count the number of messages in a particular category and the messages cannot be written to a database using EDC – something that was possible in version 4.3 of Corticon.

If you need to exercise more control over the content and disposition of such messages here is one way to do it

(it would be nice if this could be done automatically using the existing rule statements. See the following in the Ideas section )