Navigation from one interface to another interface ??

RE: Navigation from one interface to another interface ??

yp — Thu, 28 Dec 2023 08:45:12 GMT

I have one grid in that grid each row having button and on clicking on that button or link, page should be navigate to another page with selected id and open another grid not like edit page.

RE: Navigation from one interface to another interface ??

Ulises — Thu, 01 Dec 2022 16:48:14 GMT

Hi ,

Any different approach without using "user input task"??? Let's say we don't want a task and only want to display another interface, let say we have another process model with the StartForm as the new interface, how can we configure this use case?
Thanks

RE: Navigation from one interface to another interface ??

shivappak0001 — Thu, 19 May 2022 15:25:41 GMT

Thanks

RE: Navigation from one interface to another interface ??

mazharahmed — Thu, 19 May 2022 09:58:25 GMT

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.

RE: Navigation from one interface to another interface ??

GopalK — Thu, 19 May 2022 08:13:54 GMT

In this case, you can configure a button called "Next" in the first interface and in button's saveinto parameter you can update the page id for other interfaces. So once user clicks on next button the page Id will change and then based on this page id you can show your other interface. see below structure and based on it design your interface

a!localvariables(
local!pageId:1,
{
if(
local!pageId=1,
rule!interface1,
ruleInterface=2
),
}
)

RE: Navigation from one interface to another interface ??

Arul — Thu, 19 May 2022 04:53:40 GMT

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).

RE: Navigation from one interface to another interface ??

shivappak0001 — Thu, 19 May 2022 03:57:56 GMT

Hi Gopal, Thanks for the document shared. Here in document it is navigating from tab to tab. My use case is one in which i am trying to navigate to interface based on click of button. i have one interface which shows add address details once user enters details and click submit it has to navigate for another interface or it has to popup an interface for further step.

RE: Navigation from one interface to another interface ??

GopalK — Wed, 18 May 2022 13:36:06 GMT

HI Shiva, Please go through below documentation link,

https://docs.appian.com/suite/help/22.1/tabs-pattern.html

RE: Navigation from one interface to another interface ??

shivappak0001 — Wed, 18 May 2022 12:32:41 GMT

How to use links to call interfaces??.

i tried but i didnt get the expected result

RE: Navigation from one interface to another interface ??

shivappak0001 — Wed, 18 May 2022 12:03:47 GMT

Can i get more information Please, on how to navigate to another interface based on button click using link as you mentioned ??

My use case is simple i have two interfaces, first interface has button called submit . when user clicks on the button it has to go for next interview. How to achieve this using links ??

Please suggest..

RE: Navigation from one interface to another interface ??

GopalK — Wed, 18 May 2022 09:26:50 GMT

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.

RE: Navigation from one interface to another interface ??

Stewart Burchell — Wed, 18 May 2022 09:00:00 GMT

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:

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
you can also chain different User Input Tasks together in the same process flow. Chaining creates a synchronous experience for the User