Need to retain the same page after successful ending of a process

RE: Need to retain the same page after successful ending of a process

Maria — Thu, 16 Nov 2023 20:26:32 GMT

Starting a process when a user clicks on a icon, but without leaving the current interface, right now I was using a process start link but that refresh and it takes the user out. I wanted to see if there is away with what you mentioned the process start but inside a text icon.

RE: Need to retain the same page after successful ending of a process

Stefan Helzle — Thu, 16 Nov 2023 20:17:03 GMT

Do what exactly? Different things have been discussed here?

RE: Need to retain the same page after successful ending of a process

Maria — Thu, 16 Nov 2023 19:53:57 GMT

Hello! How can I do this if I'm using an Icon for the user to click and trigger the process? and I want to stay in the same interface?

RE: Need to retain the same page after successful ending of a process

Stefan Helzle — Fri, 09 Sep 2022 14:49:01 GMT

I would not go that way. Consider this when using a user input task just for displaying some interface:

appian.rocks/.../

RE: Need to retain the same page after successful ending of a process

saifalikhan13 — Fri, 09 Sep 2022 14:46:56 GMT

Got your point,
What I did is I called the child interface again before the end node of my process model, and that user input task has a 30 minutes timer to end it gracefully.
Once I am navigating, at the end it is taking me to the expected child interface only.

RE: Need to retain the same page after successful ending of a process

Mike Schmitt — Fri, 09 Sep 2022 13:52:55 GMT

[quote userid="62731" url="~/discussions/f/user-interface/25813/need-to-retain-the-same-page-after-successful-ending-of-a-process"]Any workaround on this?[/quote]

How much work are you willing to do?

The manual workaround (at least one possible one, and maybe the most robust) - which works well but is a lot of working-around, is to build a special DB table which holds a save-state, user-by-user, of which tab they're on for this site (though if you do this, i'd set it up such that it could hold such data for any/all sites that a user might access).

Upon clicking either tab card, you'd send a quick WTDS call on-form to save their "last clicked tab" (or whatever you'd like to name it). When any given user loads the interface initially, a quick query is run against that table to pull back that user's save-state entry (if any), and choose which tab to show (or show the default one if no entry is found).

Honestly, unless it's critically important that you build exactly this setup, i'd seriously consider just migrating the "delete" action to a record action (as Gabriele Camilli mentioned already), or alternatively, perhaps make it an unattended a!startProcess() call which automatically refreshes the interface but without leaving it (though you didn't say whether there are any intermediary process steps, so I have no idea whether this fits with your current usage flow).

RE: Need to retain the same page after successful ending of a process

Stefan Helzle — Fri, 09 Sep 2022 12:59:55 GMT

Do you use a startProcessLink? If yes, this is expected behaviour. The reason is, that Appian does not preserve the state of any local variable you might use to manage the state of your interface. As the process flow completes, the interface is refreshed including any local.

You can use startProcess to trigger the process in the background and stay on your interface.

RE: Need to retain the same page after successful ending of a process

Gabriele Camilli — Fri, 09 Sep 2022 12:31:31 GMT

Hi,

Could you use a Record Action instead of a Start Process?

Else you could try (if the process is very fast) to have an asynchronous process and a refresh action after that, but i would warmly suggest the first, as the second is inconsistent

RE: Need to retain the same page after successful ending of a process

Harshit Bumb (Appyzie) — Fri, 09 Sep 2022 12:30:34 GMT

This shouldn't be happening in the first place. Can you add the code for these interfaces?