Execution Type Rules

Returns a boolean evaluation result and may invoke field value setters and rule actions.

Purpose

Evaluate conditions and perform side effects such as sending notifications, calling services, writing files, enriching data, and changing state via rule actions.

Full View

Engine Behavior

  • Returns a boolean result, same as evaluation rules.
  • May invoke:
    • In‑rule methods (public value‑returning methods) inside conditions.
    • Rule actions (public void methods) declared on the source type or attached via external classes.
    • Field value setters.
    • Inline rules: other execution type rules, run from the Then / Else sections.
  • Supports Loop and Ruleset editor/evaluation modes where enabled by editor settings for iterative scenarios.
  • Not eligible for Rule-Based Data Filtering.
  • Can itself be an inline rule that other execution type rules execute.
  • Cannot be a reusable rule: only evaluation type rules can.

C# - Execution

using CodeEffects.Rule.Engine;

bool ok = new Evaluator<Order>(ruleXml).Evaluate(order);

Authoring Surface

  • Everything available to evaluation rules plus Actions and Field Setters context menus.
  • Actions and Field Setters can be invoked in Then / Else rule sections.
  • Execute... in Then / Else runs another execution type rule that its owner marked as inline (since v7). See Inline Rules.
  • Conditions can use reusable rules, as Boolean fields or method returns: evaluation type rules used as conditions.

Best practices

  • Guard side effects. Keep actions idempotent and reversible where possible; add operational safeguards and limits for loops.

Ask on Stack Overflow - Yes, it's still active
Ask in GitHub Discussions

p102

l097 --

l102

p101

×