#Milestone I have three screens with milestone on top. i was trying t

Hi michaelag,
Using "Submit link" we can submit the form. So that, we can navigate to other screens. forum.appian.com/.../SAIL_Components.html

Hope this helps, Plz check
forum.appian.com/.../SAIL_Recipes.html

@michaelag That depends. Various types of links you can use as per the documentation at https://forum.appian.com/suite/help/16.1/SAIL_Components.html#Milestone are a!documentDownloadLink(), a!dynamicLink(), a!newsEntryLink(), a!processTaskLink(), a!recordLink(), a!userRecordLink(), a!safeLink(), a!submitLink(). For instance, let's say the requirement is to navigate to other task, the you should use a!submitLink(). Let's say, the requirement is to surface some components in the same interface and hide others, then you may use a!dynamicLink() and perform some show or hide logic, the SAIL recipe at https://forum.appian.com/suite/help/16.1/SAIL_Recipes.html#Build_a_Wizard_with_Milestone_Navigation is an example for this.

It depends. If you create a single form wizard then you should use a dynamiclink. If you build a process with several UITs then the use a submitlink.
Think about general usability when building navigation items on forms. It might be better to use buttons for navigation. Mixing buttons and links for same type of navigation can be confusing for the user.

Hi michaelg, we can achieve this by one of the workaround by combining all the three interfaces in one SAIL interface and we can arrange those interface by using choose function. Now we can place dynamic link in milestone component based on the active stage value differ the interfaces will differ accordingly by mapping this value to choose selection value.

@pavang Just to let you know, the SAIL recipe (at https://forum.appian.com/suite/help/16.1/SAIL_Recipes.html#Build_a_Wizard_with_Milestone_Navigation) mentioned above has been already been designed on same lines, that is, displaying components by choose, making use of dynamic link to change step value etc.