Writing technical rules

The technical rules you write must conform to the ILOG® Rule Language structure. Technical rules can contain variable definitions, conditions, and actions.

Structure of a technical rule in IRL
When you write a technical rule, you must use the correct ILOG Rule Language structure.
Defining a variable
When you define a variable, you must use the correct ILOG Rule Language syntax.
Writing conditions in IRL
You can write simple, complex, existence, collection, nonexistence, and evaluate conditions.
Adding tests to a condition
You can write standard tests, tests on attribute values, tests on values returned by methods, and tests on values belonging to sets of values. You can write conditions with 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 anonymous inner classes syntax.
Writing a rule with an else action clause
When you write a rule with an else action clause, you must use the correct syntax.
Notifying the rule engine of object changes
You can notify the rule engine of the availability of new objects, or when an object has been updated or retracted.

Parent topic: Working with technical rules