Rule 
Definition
A rule is a tripel, consisting of the
· ID of an event
· ID of a Boolean expression
· ID of an action whose behavior is if <Expression>=TRUE then<Actions>, if it is called in the corresponding event.
For this reason, rules in the BRF do not have an independent ID.
Use
The purpose of a rule is to execute one or several actions dependent on a condition. If the condition is true, the action is executed. If it is not true, the action is not executed.
A rule is always assigned to an event. Each BRF event can contain any number of rules.
You can group rules together in rule sets.
Structure
A rule usually consists of a Boolean expression and an (abstract) action (this is the “real rule”). In this context, an abstract action stands for any number of specific actions.
However, there are also adaptations of the "real" rule. Here is a list of all the rules supported by the BRF:
· Rule consisting of an expression and an (abstract) action ("real rule")
This „real rule“ is the most common one.
It has the
following appearance: if <expression> = TRUE then <action>.
In other words, if a condition defined by the <expression> delivers the
result TRUE, the assigned <action> is executed.
· Rule that does not contain an expression, but an action (“false rule”)
If you do not store an expression, the action is always executed as soon as the event is triggered.
· Rule that contains an expression, but not an action (“false rule”)
The expression is always calculated, but no action is executed.
This rule only makes sense in the following case:
If the application that calls the event expects a result to be returned.
Integration