IF CONDITION WITH MORE THAN 3 PARAMETERS

You're absolutely right — the if() function in Appian does support more than three parameters and behaves like a multi-branch conditional. It evaluates each condition in order and returns the result of the first condition that evaluates to true. If none of the conditions are true, it returns the final default value.

Even though this usage is not explicitly documented in Appian’s official function reference, it is fully supported by the platform and commonly used by many developers in the community. It’s essentially a cleaner alternative to deeply nested if() statements.

That said, if you’re working with more complex logic or want better readability, especially with 3+ conditions, it’s worth considering the a!match() function (available from Appian 22.4 onward), which is officially documented and designed for multi-condition logic.

if(
  condition1, result1,
  condition2, result2,
  condition3, result3,
  ...,
  defaultResult
)

We have also used the if function with multiple parameters; however, during our code review with Appian before go-live, it was recommended to avoid using undocumented features since they can be deprecated at any time without prior notice. Additionally, such implementations might not be flagged by Appian design tools like the expression editor or health check, potentially leading to unnoticed issues or future compatibility problems. Therefore, it is advisable to use a!match() or choose() when handling multiple conditions.

I do not allow this in my teams. There are many edge cases where this does not work anymore. Use a!match instead.

Just to follow up — I completely agree that a!match() is the better, safer option for handling multiple conditions.
What I meant to convey is that the extended if() syntax does work and is commonly used in practice, but since it's not officially documented, there's always a chance it could stop working in future versions. So yes — it's definitely better to replace it with a!match() where possible.