<?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>Hi  I have a User Input Task in the main process model and another in</title><link>https://community.appian.com/discussions/f/user-interface/1447/hi-i-have-a-user-input-task-in-the-main-process-model-and-another-in</link><description>Hi I have a User Input Task in the main process model and another in a Sub Process and a third again in Main Process Model. All the flows are activity chained. I expected that all the three forms will be opening next to next. But the observed phenomenon</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Hi&lt;br /&gt;&lt;br /&gt;I have a User Input Task in the main process model and another in</title><link>https://community.appian.com/thread/5051?ContentTypeID=1</link><pubDate>Thu, 31 Oct 2013 14:55:24 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:85b3cda0-40c3-4ba4-ba95-9c84a6dc8499</guid><dc:creator>aayusha</dc:creator><description>Thanks all for the help. In my use case, the User Task in Sub Process was also a Quick Task. So for disabling the QT after execution of Sub Process, I was using Exception flow which was directed to end event. As soon I removed the exception flow, it worked fine. Now to disable the QT, I actually used Terminate on End Event.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Hi&lt;br /&gt;&lt;br /&gt;I have a User Input Task in the main process model and another in</title><link>https://community.appian.com/thread/5039?ContentTypeID=1</link><pubDate>Thu, 31 Oct 2013 04:13:16 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:93f50af8-d924-463d-acc8-6741e3759b85</guid><dc:creator>Eduardo Fuentes</dc:creator><description>Another suggestion: Remember that there are other two reasons why activity chain can break: You are exceeding the 50 unattended nodes limit between your two human attended chained tasks (be aware of multiple-node-instances MNI since that counts when it comes to the number of nodes) or you are exceeding the 8 seconds limit of execution in those intermediate unattended nodes. Take a look at this link for more information&lt;br /&gt;&lt;a href="https://forum.appian.com/suite/wiki/73/Configuring_Activity-Chaining#Breaking_a_Chain"&gt;forum.appian.com/.../Configuring_Activity-Chaining&lt;/a&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Hi&lt;br /&gt;&lt;br /&gt;I have a User Input Task in the main process model and another in</title><link>https://community.appian.com/thread/5037?ContentTypeID=1</link><pubDate>Wed, 30 Oct 2013 23:58:10 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:20af61e0-42ec-44ba-896a-d5cee2ef3484</guid><dc:creator>Ruth Ogala</dc:creator><description>Hi Aayush - In addition to what Patty said to do, make sure that all flow lines are chained (including the ones at the start and end events). You may have missed one of those.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Hi&lt;br /&gt;&lt;br /&gt;I have a User Input Task in the main process model and another in</title><link>https://community.appian.com/thread/5036?ContentTypeID=1</link><pubDate>Wed, 30 Oct 2013 23:24:15 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:7190603a-9fc6-42b2-a152-eb0c22e92c6d</guid><dc:creator>Patty Isecke</dc:creator><description>In the sub process properties, go to the setup tab. Do you have &amp;quot;Enable activity chaining into all initial nodes in the sub-process&amp;quot; checked?&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>