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

Hi, You can have tabs in your interface and you can configure other interfaces on click of these tabs. You can also use links to call other interfaces.

Hi,

My opinion, I would approach process model.. sample in below.  When you click the submit button in the first interface (userInput task) it will trigger to the next interface (userInput task).

As I observe this discussion, if you are required to display second interface after clicking on submit button so that thing you can manage by process model. In the process model take your first interface in process start form then use another "user input task" for your next interface and move on further as per your use case. Don't forget to use activity chaining between them. I hope it will helpful for you.

Happy Coding.