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

Question

Hi Appian Pals
Please have a look on the interface below, this is having different cards, and each card is having independent interface behind it and can be accessed using a button click.

This is also the main interface of my site.

The main issue is when I click and open the child interface from this card, I have a grid which is having synchronous process for deletion of record.

But after the successful completion of the process, it is brining back to the main home interface instead of the child interface.

Again I am back to the main interface, instead of the child interface
The process should end on the interface where it started.

Any workaround on this?

Mike Schmitt · Answer

Unknown said: Any workaround on this? 
 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).

Gabriele Camilli · Answer

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

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

Top Replies