Rule Evaluation Without Suitable Alternatives

  • Updated

This document describes how to create rule evaluation requests without suitable alternatives.

In some rules, fallback branches comprise a set of negated options.

You can verify this in many regulatory properties of type Country.


The screenshot below shows an example with the Present Client Country property with the Outside CAN and Inside CAN branches.

The inside case is defined as presentClientCountry == CAN (meaning that the present client Country equals Canada).

The outside case is the negation of the inside case: presentClientCountry != CAN (meaning that the current client Country does not equal Canada).

presentclientproperty with branches

In such cases, Apiax recommends using the following best practice:

  • Use the value __ (double underscore) to denote:

    • the outside Country or jurisdiction case (regulatory properties of type Country)

    • the case of none of the possible options (regulatory properties of type Text)
      __ means non-existing-country / jurisdiction.

  • For regulatory properties of type Text, use the value _other_. This value is a convention to follow when creating a rule and defining branch options.
    No rule must ever use the option _other_ in its definition.

For evaluating the case above, there are two alternatives:

  1. If you know the current client country, you can specify that value. For example, GBR which is != CAN. The attribute looks like this:


  2. Alternatively, you can use __ to specify that it is not CAN even if you do not know which country it is. This also triggers the outside path since __ != CAN. The attribute looks like this:



Related documents

Refer to the following documents for additional information and details about Rule Evaluation.


Was this article helpful?

0 out of 0 found this helpful



Article is closed for comments.

Still have questions?

Please submit a request and we will get back to you shortly.

Submit a request