<?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>Timer and Activity Chain</title><link>https://community.appian.com/discussions/f/process/38128/timer-and-activity-chain</link><description>Hi, 
 I&amp;#39;m trying to insert a timer in a process model (like that simplified in the screenshot belowe), but with the timer the chain between first and second User Input Task stop working, the second UIT doesn&amp;#39;t appear (only in Tempo). The same behavior</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Timer and Activity Chain</title><link>https://community.appian.com/thread/143504?ContentTypeID=1</link><pubDate>Mon, 09 Dec 2024 17:20:30 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:47653392-7aed-4abe-972e-c80f0ba15df1</guid><dc:creator>Gabriele Minardi</dc:creator><description>&lt;p&gt;OK, I think I&amp;#39;ll use one of the tricks you mentioned, the problem is at the database level (due to a trigger and a sequence that do not allow a quick synchronization of the cdt that the process uses).&amp;nbsp;Maybe a refresh button in the second node..&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Timer and Activity Chain</title><link>https://community.appian.com/thread/143501?ContentTypeID=1</link><pubDate>Mon, 09 Dec 2024 15:46:32 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:2ab0f251-b720-4bad-b422-b361df2f2e8d</guid><dc:creator>Mike Schmitt</dc:creator><description>&lt;p&gt;Where is that calculation taking place?&amp;nbsp; If you put it in a Script Task node between the two tasks, the chaining will wait for it (up to a reasonable extent) - keep in mind though that as far as what the user sees during this time, they&amp;#39;ll just be stuck with a &amp;quot;loading page&amp;quot;.&amp;nbsp; For things that take even longer than that, I&amp;#39;ve sometimes resorted to making an intermediary task which the user sees during the &amp;quot;loading&amp;quot; process, where their only input is a &amp;quot;refresh&amp;quot; button, which (while the process flow is still waiting) just loops them back to the same form, but then eventually takes them on to the second task.&lt;/p&gt;
&lt;p&gt;For any more detailed advice though we&amp;#39;d need to know more about what the calculation is, where it&amp;#39;s happening and why, and how long it&amp;#39;ll be expected to take in an average use case.&amp;nbsp; Sometimes it&amp;#39;s better, for instance, to simply allow the user to see their subsequent task separately when it&amp;#39;s ready, i.e. it pops up on their task list once the background process has accomplished what it needs to.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Timer and Activity Chain</title><link>https://community.appian.com/thread/143500?ContentTypeID=1</link><pubDate>Mon, 09 Dec 2024 15:41:12 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:6c77665b-faa4-495e-bf85-dd8ac3e2cdcb</guid><dc:creator>Gabriele Minardi</dc:creator><description>&lt;p&gt;Thanks Mike, I&amp;#39;m trying to create a delay before the second node, because it needs to display a query result that a MS SQL calculation takes a while to render after the first node.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Timer and Activity Chain</title><link>https://community.appian.com/thread/143499?ContentTypeID=1</link><pubDate>Mon, 09 Dec 2024 15:32:45 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:430614ba-0729-4719-a15b-e1ed80bcaddd</guid><dc:creator>Mike Schmitt</dc:creator><description>&lt;p&gt;Timers break activity chaining by definition.&amp;nbsp; The second node (once the timer&amp;#39;s condition is satisfied) would start and be assigned to whoever is defined in the node&amp;#39;s assignment configuration.&lt;/p&gt;
&lt;p&gt;What exactly are you trying to accomplish?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>