🧰 Tools
Rule Type
Each rule type receives a different set of input arguments. This is the detail that
examplerules.xml is usually consulted for.| Argument | Type | Meaning |
|---|
Rule Name
Generated XML
Deploy with the iiq console:
import /path/to/rule.xml from IdentityIQ_HOME/WEB-INF/bin. Verify the argument list against WEB-INF/config/examplerules.xml for your IdentityIQ version before relying on it.Workflow
Steps
Transitions are generated in order, each falling through to the next step. A bare default transition is always emitted last so the workflow cannot dead-end.
Generated XML
Task Definition
Compile into a JAR, drop it in
WEB-INF/lib/, then restart the application server — classes there are not hot-reloaded.Generated XML + Java skeleton
The
terminate() method is not optional. A task that ignores it cannot be stopped from the UI, leaving an administrator with only an application server restart.BeanShell Compatibility Check
BeanShell interprets Java 1.4-era syntax. Modern Java constructs parse fine in your IDE and then fail at runtime — often months later, the first time an untested branch executes. Paste rule source here to catch them first.
