There are three types of task that a ruleflow can contain:
-
Rule task
- A rule task references a set of rule providers, that is, a rule package, a rule, a decision table, a decision tree or a combination. From each of these rule providers, the extractor cookie of the deployer will extract some execution rules. A rule task in the repository will be mapped to a
ruletask
statement in IRL. The body of the IRL ruletask
will be composed of the names of all the extracted execution rules. -
Function task
- A function task is made of a piece of IRL code that will be executed each time the task is executed. A function task in the repository will be mapped to a
functiontask
statement in IRL. The body of the IRL functiontask
will be made of the text of the IRL definition of the function task. -
Subflow
- A subflow (or flow task in IRL) is a set of tasks, similar to a ruleflow, defined as a subunit. Like a ruleflow, a subflow has three possible representations: ruleflow, IRL, and code.
- A subflow in the repository will be mapped to a
flowtask
statement in IRL. The body of the generated IRL flowtask
will be made of the text of the IRL definition of the subflow.
See Also
Setting a New Ruleset Extractor Class | Defining Ruleflows | Creating a Ruleflow
|