Navigation from one interface to another interface ??

it depends on the context of what you're trying to achieve. Appian Records provide different "Views" that you can navigate between by clicking on the relevant tab. You can provide links to Appian Record Views from any other Interface. Conceptually these are just web pages that you are hopping between.

If you are wanting to navigate between interfaces in the context of a process (i.e. to capture or edit some data) then you can achieve this in two different ways:

1. you can implement different interfaces in the scope of a single User Input Task. SAIL code can let you show/hide any scope of your user interface, so you can build wizard-like flows in the same physical user interface
2. you can also chain different User Input Tasks together in the same process flow. Chaining creates a synchronous experience for the User

it depends on the context of what you're trying to achieve. Appian Records provide different "Views" that you can navigate between by clicking on the relevant tab. You can provide links to Appian Record Views from any other Interface. Conceptually these are just web pages that you are hopping between.

If you are wanting to navigate between interfaces in the context of a process (i.e. to capture or edit some data) then you can achieve this in two different ways:

1. you can implement different interfaces in the scope of a single User Input Task. SAIL code can let you show/hide any scope of your user interface, so you can build wizard-like flows in the same physical user interface
2. you can also chain different User Input Tasks together in the same process flow. Chaining creates a synchronous experience for the User