Congratulations on completing the Corticon Advanced Rule Modeling Tutorial! You have learned to incorporate some of Corticon Studio’s more powerful functionality into your rule modeling process, including:

Building a Vocabulary – Based on the analysis of a business problem, you’ve learned how to identify the Vocabulary entities, attributes, and associations that are needed for rule modeling, and build the Vocabulary in Corticon Studio.

Scope and Aliases – Scope tells the Corticon rules engine which data to use when evaluating and executing rules. You’ve learned to define Scope for a Rulesheet and define an Alias to represent a scope perspective in your rules.

Collections and Collection Operators – A Collection is comprised of one entity associated with one or more other entities, called elements of the collection. Collection Operators operate on groups of entities rather than individual entities. You’ve learned how to use Collection operators to operate on collections in rules. You also learned that it is mandatory to use Aliases to represent collections.

Action-only rules in column 0 – You’ve learned how to use column 0 to define non-conditional rules. Column 0 rules can be used to perform calculations that contribute data to other rules in the Rulesheet, or in downstream Rulesheets in the same Ruleflow.

Filters – You’ve learned how to define Filter expressions to limit data being evaluated to only the subset that survives the filter. A filter does not permanently remove or delete any data, it simply excludes data from evaluation by other rules in the same Rulesheet.

Sequencing Rulesheets using Ruleflows – You’ve learned how to create a Ruleflow, add Rulesheets in a sequence, and test the Rulefllow. If a natural sequence or “flow” of logical steps can be identified within a single decision step, it often makes sense to organize the flow using separate Rulesheets for each logical step. Rulesheets will execute in a sequence determined by their order in the Ruleflow. Using multiple Rulesheets helps you visualize the logic and maintain and reuse them more easily.

Transient Attributes – You’ve learned how to use Transient attributes in your rules. Transient attributes are used as “intermediate” value holders that do not need to be returned in a response.

Embedding Attributes within Rule Statements – You’ve learned how to embed attributes within rule statements to make rule messages more meaningful.