Use a collection to model business logic and implement common rule engine patterns. Collections define an ordered sequence of rules, the conditions under which they execute, and postprocessing steps known as response actions. The business-friendly options on this form help you to quickly develop flexible solutions that are easily understood by various audiences.

• Collection rules
• Completing the Basic/Advanced Collection tab

  Complete the fields on this tab to define the sequence of steps the collection processes at run time. Each step can call a supported rule, set property values, or stop collection processing.

• Completing the Preamble and Stop tab

  Complete the fields on this tab to define pre-actions and post-actions that are evaluated before and after the collection is processed.

• Completing the Specifications tab

  Complete the fields on this tab to create a link between a specification and this collection. Rules that are linked to a specification are implementations.

• Using conditions in a collection

  Add conditions to your collection to support multiple paths of execution.

• Setting the context of a collection step

  Each step in a collection has a context, or primary page, that determines the rules and data it can reference. The context of a collection step is analogous to the step page of an activity step.

• Using response actions in a collection

  Use response actions to call rules or methods after a collection step completes processing.

• Rule type
• Unit testing a collection

  You can test a collection individually, before testing it in the context of the application that you are developing.