Best practices for Creating Sail

 

 Best Practices for Appian developers

Appian best practices are like a check list, use these checklists at different stages of your development cycle as described to ensure application success and reduce technical risk. Each section provides guidance for when and how often you should use these.

10.Best practices for Creating Sail :-

1.Format all the SAIL code expressions.

2.Comments to be present in every SAIL rule indicating the purpose/function of the major components.

3.Identify and Design reusable SAIL interfaces

4.Identify and move common interfaces or sections into reusable rules.

5.Use local variables instead of rule input (ri) for saving manipulations, unless you need to pass the value to parent rules.

6.Use smart service functions on button actions wherever possible.

7.Create reusable custom components.

8.Always set default test values for Interface rules, so that the Live View is visible.

9.Use Decisions instead of nested/multiple if conditional validations.

10.DO NOT call SAIL expression directly in expression editors, instead create separate interface rules and map the same.

11.SAIL interfaces should not contain more than 20 inputs

12.DO NOT use dynamic behavior for offline forms.

13.Use form validation messages for problems that are not specific to a single component.

14.DO NOT have database calls in ‘with()’ function or inside a looping function like a!forEach.

15.Either a billboard layout may have a bar overlay or a column overlay.

16.Use ‘showWhen’ parameters instead of complex if, else condition to hide or show components.

17.Use Decision components instead of complex expression rules.

18.Use pagination in grids to avoid all the data displayed in a single page.

19.Use validation groups for multiple rule validations.

20.Avoid mixing box layouts and section headings.

21.Always left align grid columns for better readability.