Business rule language
You use the constructs, operators, and time windows of the business rule language to write rules.
- when part
The constructs in the when part define the events to process. - definitions part
The definitions part introduces local variables that you can use in the rest of the rule. - if part
The if part introduces the condition of the rule. - then and else parts
The then and else parts introduce actions that the rule completes when an event is processed or when a condition is met. - Aggregation operators
You can use aggregation operators over a collection of objects. Aggregation operators calculate the average, total, minimum, or maximum value of the numeric attributes in a collection of objects, or the number of objects in a collection. - Arithmetic operators
Arithmetic operators perform operations on numbers and text. You can use them in variable definitions, conditions, and actions. - Geospatial operators
You can write rules to reason over geographic locations. - Logical operators
Logical operators associate conditions. They perform logical operations on the Boolean values returned by these conditions. - Number operators
Number operators define conditions based on numbers. - Object operators
Object operators define conditions based on objects (as opposed to attributes of objects). A customer is an object; the age of the customer is an attribute of the customer object. - Text operators
Text operators define conditions based on strings. - Time operators
To include time logic to the rules, you use event and time operators. These operators can express durations, time points, time periods, and current time. - Time value types
You can use the Date, Simple Date, and Universal Date, and Time value types to express time values. - Numbers
Number types are represented as a set of digits with a possible decimal point separator, a grouping symbol, a minus sign and an exponent. - Strings
String literals are represented by a set of characters enclosed in double quotation marks ("Text string"). - Punctuation in rules
The business rule language uses punctuation to identify specific language artifacts and to avoid ambiguous syntax. When you edit business rules (for example, in the Intellirule editor), mandatory punctuation is usually predicted in the completion menu. - Vocabulary view
The Vocabulary view displays the vocabulary of a solution project. This vocabulary comprises the rules and agents verbalizations in the business object model of the project, and the vocabulary available in the system.
Parent topic: Reference