To conditionally execute a formula based on a boolean isCustomer, which approach should be used?

To conditionally execute a formula based on a boolean isCustomer, which approach should be used?

• A. Use a single Calculation Step with an IF statement directly in the formula definition to reference the isCustomer variable and conditionally perform the appropriate calculation.
• B. Use two separate Calculation Steps with the Conditional Step property selected; reference just the isCustomer variable in the Condition syntax (no comparison necessary).
• C. Use two separate Calculation Steps with the Conditional Step property selected; use the ISTRUE(isCustomer) and NOT(ISTRUE(isCustomer)) functions in the Condition syntax.
• D. Use two separate Calculation Steps with the Conditional Step property selected; the Condition syntax should reference a different variable.

Answer: (C)

Conditionally executing a calculation based on a boolean isCustomer means wiring two separate calculation steps and using the Conditional Step feature to choose which one runs. The best approach is to have one step execute when the boolean is true and another when it is false, using explicit tests: ISTRUE(isCustomer) for the first path, and NOT(ISTRUE(isCustomer)) for the second. This makes the flow clear and ensures only the appropriate calculation runs for each value of isCustomer. Using a single calculation step with an IF inside the formula can work, but it doesn’t leverage the conditional-step pattern across multiple steps, which is what this approach is designed for. Relying on just referencing the boolean variable in the condition is less explicit and can be ambiguous in how the framework evaluates the condition. Referencing a different variable in the condition would not correctly reflect the isCustomer state to drive the two-step flow.

Conditionally executing a calculation based on a boolean isCustomer means wiring two separate calculation steps and using the Conditional Step feature to choose which one runs. The best approach is to have one step execute when the boolean is true and another when it is false, using explicit tests: ISTRUE(isCustomer) for the first path, and NOT(ISTRUE(isCustomer)) for the second. This makes the flow clear and ensures only the appropriate calculation runs for each value of isCustomer.

Using a single calculation step with an IF inside the formula can work, but it doesn’t leverage the conditional-step pattern across multiple steps, which is what this approach is designed for. Relying on just referencing the boolean variable in the condition is less explicit and can be ambiguous in how the framework evaluates the condition. Referencing a different variable in the condition would not correctly reflect the isCustomer state to drive the two-step flow.