![]() ![]() |
|
Help for Rules Engine Administration | |
Search | Index | |
![]() |
|
![]() |
![]() |
![]() |
Using Rules EngineThe Rules Engine is an optional feature that enables process designers and business analysts to create and add business rules to workflows. Business rules are associated with the individual steps of a workflow in Process Designer but are created in ILOG JRules, a third party application purchased separately from Process Engine. Each step in a workflow can have multiple rules that execute at different stages of the step. The user specifies when a rule is to execute by setting its type; rules can be set to run Before Execution, On Save, or After Completion. When a running workflow encounters a rule, Process Engine sends a request to the Rules Engine, also know as the Rules daemon, to execute a rule set. Rules Engine executes the rules in the rule set and returns the results to the Process Engine. NOTE If the Rules daemon is stopped when a workflow tries to run a rule, the Process Engine executes the Malfunction map. The default behavior for this map is to place the workflow in the Conductor queue. To view or manage items in the Conductor queue use vwtool or the Process Administrator. NOTE If
the Rules Engine interface is disabled,
workflows will run but will ignore any rules
called by the workflow. See Enable Rules Engine
Integration in the Installation Guide
for instrustions. See About Business Rules for more information on using business rules in workflows. Implement rules functionality in a workflow definitionUse the following general steps to implement rules
|
![]() |
|
![]() |
|