Controlling the actions of a rule
Each rule can have one or more actions to be executed in sequence. An action can consist of the following various forms:
Predefined function invocation:
function_name(argument1, argument2,…);
Invocation of the BP Server API, in order to control process instances, get status info, etcetera.
Generating and sending an e-mail.
Generating internal events that trigger other rules.
An infopad operation, that is, value assignment:
ReqStats[2][4].name := event1.name;
An administration operation, that is, like discarding used events from the event cache.
In this section:
