<?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>refresh Scree with no Buttons</title><link>https://community.appian.com/discussions/f/user-interface/18010/refresh-scree-with-no-buttons</link><description>We have a situation, where user upload a document, after he hits a upload button on screen1 in back end a PDF Converter will gets triggered. until the uploaded doc got converted user will be seeing a screen2, where he has a refresh button, up on hitting</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: refresh Scree with no Buttons</title><link>https://community.appian.com/thread/70842?ContentTypeID=1</link><pubDate>Thu, 05 Dec 2019 22:27:29 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:ded6a376-06e9-4d0f-a425-d877ccf23661</guid><dc:creator>Mike Schmitt</dc:creator><description>&lt;p&gt;Can you just have the original task submit, and chain the user through the PDF document generation, so that when they reach the next task the generation is complete?&amp;nbsp; It sounds like your customer is OK with this taking a few moments to complete (you can also use confirmation pop-ups on your buttons to make sure the users know it&amp;#39;ll take a minute).&lt;/p&gt;
&lt;p&gt;At this moment Appian has no official method for &amp;quot;auto submitting&amp;quot; a form.&amp;nbsp; The best techniques I&amp;#39;ve seen are either using a looping refresh button (like what you&amp;#39;re already doing), or providing a &amp;quot;dismiss&amp;quot; button for the user to close that task and then the next one will appear on their task list when the generation is completed.&amp;nbsp; Obviously neither of these is as automatic as what they&amp;#39;re asking for, but those are the constraints we work with.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>