Evaluate() Returns False When Else-If Condition Evaluates True

[Rombicon]

We are encountering what appears to be an issue with rule evaluation involving else if branches and could use some direction.

Versions

CodeEffects.Rule.Common 5.0.8.2
CodeEffects.Rule.Engine.Standard 5.0.19.3

Issue

Based on the CodeEffects documentation, the Evaluate() method should return true when any rule branch evaluates to true. If the initial if condition evaluates to false, subsequent else if branches should be evaluated, and the rule should return true if one of those branches matches.

However, we are observing behavior where an else if condition evaluates to true, but the overall rule evaluation returns false.

Reproducible Example

The following simplified rule demonstrates the issue:

If Age = 18, the rule evaluates to true as expected.
If Age = 23, the else if condition evaluates to true, but the rule evaluates to false.

XML

    xmlns:ui="http://url6609.codeeffects.online/ls/click?upn=u001.oiU71QPPSu06tYIf8OLC2wEpjACOgEDvWhG1AQ0d0y49DaChS-2BsTUCvxn-2FiGfp0evQ5G_2C9kj0upxMObWw1Pw1sux0icvXql336j2d2TwJQ5-2FIiqfDngwXPYVHJ5oTdixJXeQKzxfh15ZYjhPTgs-2FXWPGhrFTk5mc-2F4oJzIVx1WV7efc7b7z-2B-2B4NhbWpVIy-2BQFwyVYqeAM1JqR7unZeIkUKLLQhH0QHJT0ZJJko67AOtc9w-2Fu31QtK8wgiJdEZOLNcxdRkJ7dkkijQ1dpAMAH9-2BHASLwSpadLF-2FMlaivlCCx5g8-3D>
    <rule id="cfbd23c6-e4be-496b-9b65-a8705835d4ca" webrule="5.1.16.4" utc="2026-07-13T16:20:01.5969" type="ErsInfrastructure.Objects.RuleSourceObject, ErsInfrastructure, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" eval="false">
        <name>Else If Test</name>
        <description>Else If Test ERS-928</description>
        <definition>
            <if>
                <clause>
                    <condition type="equal">
                        <property name="Age" />
                        <value type="numeric">18</value>
                    </condition>
                </clause>
                <then>
                    <method name="RejectOrder" />
                </then>
                <else>
                    <if>
                        <clause>
                            <condition type="equal">
                                <property name="Age" />
                                <value type="numeric">23</value>
                            </condition>
                        </clause>
                        <then>
                            <method name="RejectOrder" />
                        </then>
                    </if>
                </else>
            </if>
        </definition>
        <format>
            <lines />
        </format>
    </rule>
</codeeffects>

Can you confirm whether this behavior is expected, whether there are any additional evaluation settings required for nested else if branches, or whether this may be a defect in our rule XML?

Hello,

The engine follows the standard .NET evaluation behavior for if / else if / else blocks and returns true only when the initial if condition evaluates to true.

Any else if clauses are treated as nested subclauses. Therefore, the runtime returns false for the overall evaluation even when setters or rule actions within an else if or else clause are invoked. In other words, the initial if condition determines the rule’s return value; execution of any subsequent clause does not change it.

The engine passes the compiled rule to the runtime, which effectively interprets it as follows:

if (condition1)
{
    action1();
    return true;
}
else
{
    if (condition2)
    {
        action2();
    }
    else
    {
        action3();
    }

    return false;
}

The editor cannot display the rule in this nested form because it must show action1, action2, and action3 at separate levels, with each action appearing after its corresponding THEN clause. This difference between the visual representation and the compiled evaluation logic caused the confusion.

You have two possible options:

1. Convert existing execution-type rules that rely on the return value to Ruleset mode (see details on rule editor modes at https://codeeffects.com/decision-automation/business-rule-editor-modes). Rulesets treat each level as a separate rule and therefore do not have this issue.
2. Add a bool Success property to your source object, set it at each level before invoking the corresponding action, and check its value after the evaluation is complete.

Please let us know if you need any further assistance.