Appian promotes navigation sidebars which gives you a possibility to have multiple interfaces on one page on one side. I really like this approach and patter but our users complains on 2 things:
1 State is not saved - when user click on something to start process (startProcessLink) then when process is done user is redirected to main page (filters are gone, Appian does not remember from which page user stared that process.
2 If you save 'state' to table (fact that user was on particular ui) then users cannot use Application on 2 or more Chrome tabs. Appian gets their state from db and move them back to same page on all tabs.
Any thoughts how to address this lost state problem?
Navigation patter:
docs.appian.com/.../secondary-navigation.html
Discussion posts and replies are publicly visible
For #1 - The only workaround I know is to never use anything that redirects to another page. You must do your saves inline (via startProcess tied to a button), alternatively, you can use Record Actions, but they need to be in Dialog mode.
For #2 Stems from the fact that we cannot create urls other than for Sites or Record views. There's no way to point a user to a secondary page with a URL.
Don't save the state in a table. Rather use the cache plugin. It's much lighter and build for such use cases only.
Unfortunately business expect to have file upload comment which requires button to be marked as submit button. Version 23.2 introduced another way to upload file.
Yes, with 23.2, you will be able to submit files without a Start Form or User Input Task so it might help with this.
appianspace.com/.../