Which is Appian best practice for calling interface rules on your interface?

Which is Appian best practice for calling interface rules on your interface?

• A. Call the interface rule directly by name without syntax
• B. Use keyword syntax
• C. Create a REST integration
• D. Duplicate the interface rule's logic

Answer: (B)

Calling interface rules using keyword syntax is the preferred approach because it passes inputs by explicit names, making the call clear and resilient. When you use named parameters, the order of inputs doesn’t matter, which reduces errors if inputs are added or reordered in the rule later. It also makes optional inputs straightforward: you can omit them or specify only what you need, while keeping the call readable. Other approaches don’t offer the same benefits. Calling an interface rule by name without proper syntax can lead to ambiguity and is not how Appian expects rule calls to be made. Creating a REST integration serves external communication needs and isn’t about how you call interface rules from within Appian. Duplicating the interface rule’s logic goes against reuse and maintainability—relying on a single, properly called interface rule keeps your app DRY and easier to maintain. So, using keyword syntax to call interface rules best supports clarity, maintainability, and future-proofing of your interfaces.

Calling interface rules using keyword syntax is the preferred approach because it passes inputs by explicit names, making the call clear and resilient. When you use named parameters, the order of inputs doesn’t matter, which reduces errors if inputs are added or reordered in the rule later. It also makes optional inputs straightforward: you can omit them or specify only what you need, while keeping the call readable.

Other approaches don’t offer the same benefits. Calling an interface rule by name without proper syntax can lead to ambiguity and is not how Appian expects rule calls to be made. Creating a REST integration serves external communication needs and isn’t about how you call interface rules from within Appian. Duplicating the interface rule’s logic goes against reuse and maintainability—relying on a single, properly called interface rule keeps your app DRY and easier to maintain.

So, using keyword syntax to call interface rules best supports clarity, maintainability, and future-proofing of your interfaces.