Writing technical rules

Your technical rules must conform to the ILOG® Rule Language (IRL) structure. Technical rules can contain variable definitions, conditions, and actions.

Writing the basic structure of a technical rule in IRL
When you write a technical rule, use the ILOG Rule Language structure.
Defining a variable
When you define a variable, use the ILOG Rule Language syntax.
Writing conditions in IRL
You can write simple, complex, existence, collection, nonexistence, and evaluate conditions. To write conditions, use the ILOG Rule Language syntax.
Adding tests to a condition
You can write standard tests, tests on attribute values, tests on values that are returned by methods, and tests on values that belong to sets of values. You can also write conditions in join tests.
Using objects that are not in memory in a condition
When you write conditions, you can use objects that are not in memory by referring to relations from objects that are available.
Writing actions in IRL
When you write rule actions, use the same syntax as a Java™ method body, except for the syntax for anonymous inner classes.
Writing a rule with an else action clause
When you write a rule with an else action clause, use the ILOG Rule Language syntax.
Notifying the rule engine of object changes
You can notify the rule engine of the availability of new objects, or when an object is updated or retracted.

Parent topic: Working with technical rules