Glossary:Collection

Collection, collection

An ordered sequence of rules to run. In each step of a collection, you can define a precondition that is evaluated before execution, and a response action that runs after the step is completed.

An ordered sequence of rules to run. In each step of a collection, you can define a precondition that is evaluated before execution, and a response action that runs after the step is completed.

An ordered sequence of rules to run. In each step of a collection, you can define a precondition that is evaluated before execution, and a response action that runs after the step is completed.

The basic building blocks of an application, rules define the behavior of an application. There are many types of rules, each defining a different type of behavior. For example, rules define the display of a form, the fields that are used in your application, and the flows that define the process of completing work.

The system can reuse rules throughout your application. For example, in an application for ordering replacements parts, you can define a user interface to capture an address, and reuse the same rule for the UI to capture both the mailing address and the billing address for the order.

You define rules in an application to create a business solution for your organization and customers. Rules provide flexibility during the development process and help you design applications more efficiently, so that they can be implemented again in future projects.

A reference to a when condition rule (Rule-Obj-When rule type) or an expression that is associated with one step of an activity. After the previous step of an activity runs, before the method in the current step runs, the system evaluates whether the rule or expression is true or false, and performs user-specified behavior based on the result.