<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.appian.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Saving UI state to DB on every user interaction</title><link>https://community.appian.com/discussions/f/user-interface/29348/saving-ui-state-to-db-on-every-user-interaction</link><description>Hello, 
 I have a requirement where I have to save the user state of the interface/page into DB and load it back when user comes back to that interface/page. For example, if the interface has tabs, then I want to save the active tab the user is looking</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Saving UI state to DB on every user interaction</title><link>https://community.appian.com/thread/116396?ContentTypeID=1</link><pubDate>Tue, 18 Jul 2023 11:51:26 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:8b717f89-0f98-451f-86d5-800a43975a7b</guid><dc:creator>Stefan Helzle</dc:creator><description>&lt;p&gt;You are welcome :-)&lt;/p&gt;
&lt;p&gt;Correct.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Saving UI state to DB on every user interaction</title><link>https://community.appian.com/thread/116382?ContentTypeID=1</link><pubDate>Tue, 18 Jul 2023 10:30:53 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:96d2dbd9-3188-4fca-8ba9-0c0ce118b6dd</guid><dc:creator>Rahul SP</dc:creator><description>&lt;p&gt;I misunderstood. Thanks for clearing that.&lt;/p&gt;
&lt;p&gt;Triggering processes in the background can again only be done inside a saveInto block right?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Saving UI state to DB on every user interaction</title><link>https://community.appian.com/thread/116378?ContentTypeID=1</link><pubDate>Tue, 18 Jul 2023 09:57:54 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:c3f69808-d022-40c0-ab71-0962b7f61400</guid><dc:creator>Stefan Helzle</dc:creator><description>&lt;p&gt;No. Use that interface just as an interface. Manage state and data in the UI and trigger processes in the background as needed. Or use record actions depending on your specific requirements.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Saving UI state to DB on every user interaction</title><link>https://community.appian.com/thread/116377?ContentTypeID=1</link><pubDate>Tue, 18 Jul 2023 09:53:35 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:4221b922-dbcf-456f-b24e-6b49c8feac51</guid><dc:creator>Rahul SP</dc:creator><description>&lt;p&gt;If I am understanding it right, what you are suggesting is to use the dashboard interface as a SAIL start form and trigger other processes as required on user action. In this case we can use process variables to store the state of the UI.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Is my understanding right?&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Saving UI state to DB on every user interaction</title><link>https://community.appian.com/thread/116231?ContentTypeID=1</link><pubDate>Fri, 14 Jul 2023 10:50:39 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:afb9cf98-7077-4ada-9d54-95b7e73bb310</guid><dc:creator>Stefan Helzle</dc:creator><description>&lt;p&gt;In Appian, you can easily&amp;nbsp;build nested UIs. So, why not just embed the UI of that to be started process in that dashboard and initiate the actual process in the background. Then you have full control on what happens in regard to UI state management.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Saving UI state to DB on every user interaction</title><link>https://community.appian.com/thread/116223?ContentTypeID=1</link><pubDate>Fri, 14 Jul 2023 10:13:55 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:325a10b2-aa18-4784-9f39-d431ea9a4c25</guid><dc:creator>Mathieu Drouin</dc:creator><description>&lt;p&gt;1 startProcess per screen. All the nodes Write DB nodes (or other nodes, sub processes) are contained in that process.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Saving UI state to DB on every user interaction</title><link>https://community.appian.com/thread/116221?ContentTypeID=1</link><pubDate>Fri, 14 Jul 2023 09:57:04 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:9bee314f-15d8-41fb-a14e-f19b43aace70</guid><dc:creator>Rahul SP</dc:creator><description>&lt;p&gt;This would require significant effort if my understanding is right. For example, if a screen has 5 different startProcess&amp;#39; which trigger 5 different process models, then it would require me to modify all those 5 process models to first save the user state and then perform the actual operation that the user wants to perform.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Saving UI state to DB on every user interaction</title><link>https://community.appian.com/thread/116220?ContentTypeID=1</link><pubDate>Fri, 14 Jul 2023 09:52:18 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:16172fa5-a11b-4a2a-bb5e-75ad12d4fbda</guid><dc:creator>Mathieu Drouin</dc:creator><description>&lt;p&gt;Have you tried using startProcess where you can call a process and put all the different operations that you want?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>