BooleanEquals

• If both properties are equal, then returns boolean of true.
• If both properties are null, then returns boolean of true.
• If only one property is null, then returns a boolean of false.
  
  Null handling tip: If there's a chance either flag might be unset, remember that two nulls return true, but one null and one non-null return false — so build your ruleset logic accordingly.

Use Case

A common use case is conditional routing or validation checks within a ruleset, meaning you compare the result of a previous boolean-returning action to an expected true/false value to decide what happens next.

Example scenario: Order approval gate

Suppose your integration has an earlier action that checks whether an order has been approved (stored as a Boolean variable isApproved). You want to route processing differently depending on whether approval is confirmed.

Result: Returns true - the order is approved, so the ruleset proceeds down the "approved" path (e.g. generate a shipping label).

If isApproved came back as false, BooleanEquals would return false, and the ruleset could branch to a rejection or hold workflow instead.

Why use BooleanEquals instead of just IsTrue?

BooleanEquals is particularly useful when you're comparing two dynamic boolean variables - for example, checking whether two systems are in agreement:

This lets you confirm both flags match before triggering a downstream process, rather than simply checking that one of them is true.