<?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>Appian Task</title><link>https://community.appian.com/discussions/f/new-to-appian/38857/appian-task</link><description>Hi Everyone, 
 I am handling the task assignment through database tables. But when two users will click simultaneouly on the link which will start the process model. How to ensure that only one user should be given the task.</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Appian Task</title><link>https://community.appian.com/thread/146997?ContentTypeID=1</link><pubDate>Tue, 08 Apr 2025 13:52:22 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:2abb2844-c432-4338-9b78-3c7e19d453c6</guid><dc:creator>Mike Schmitt</dc:creator><description>&lt;p&gt;There&amp;#39;s no bre-built process locking to &amp;quot;apply&amp;quot;, maybe i chose a misleading term.&amp;nbsp; What I meant is that you should build your process to handle the locking for you.&lt;/p&gt;
&lt;p&gt;In the process after any user attempts to click into the &amp;quot;task&amp;quot; in question, the very first thing that should happen is for the process to query the relevant DB table to check whether another user has already accessed the &amp;quot;task&amp;quot;, and if so, divert the process flow to an alternate task explaining that this task is in use by another user.&amp;nbsp; If not, the very next thing it should do is write the locking value immediately back to that same table, before proceeding on to the user input task or any other pre-task processing.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Appian Task</title><link>https://community.appian.com/thread/146993?ContentTypeID=1</link><pubDate>Tue, 08 Apr 2025 13:19:03 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:faaefa0f-db94-4c0d-8a81-7491327bf0ec</guid><dc:creator>Stefan Helzle</dc:creator><description>&lt;p&gt;&lt;a id="" href="https://docs.appian.com/suite/help/25.1/Configuring_the_User_Input_Task.html"&gt;https://docs.appian.com/suite/help/25.1/Configuring_the_User_Input_Task.html&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Appian Task</title><link>https://community.appian.com/thread/146992?ContentTypeID=1</link><pubDate>Tue, 08 Apr 2025 13:03:20 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:831fb45c-6592-45a4-b27d-fb1290afdddf</guid><dc:creator>Rahul009</dc:creator><description>&lt;p&gt;Hi &lt;a href="/members/stefanhelzle0001"&gt;Stefan Helzle&lt;/a&gt;&amp;nbsp;,&lt;/p&gt;
&lt;p&gt;can you please direct me to some tutorial to implement process task?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Appian Task</title><link>https://community.appian.com/thread/146988?ContentTypeID=1</link><pubDate>Tue, 08 Apr 2025 11:17:50 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:bd5329fe-98e7-458f-903e-a352c56fe61c</guid><dc:creator>Rahul009</dc:creator><description>&lt;p&gt;Hi &lt;a href="/members/mikes0011"&gt;Mike Schmitt&lt;/a&gt;&amp;nbsp;,&lt;/p&gt;
&lt;p&gt;Can you please help me how to apply process locking to avoid such instances?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Appian Task</title><link>https://community.appian.com/thread/146971?ContentTypeID=1</link><pubDate>Mon, 07 Apr 2025 15:46:02 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:cb50f751-21f9-4d8a-90df-a1455e86fc52</guid><dc:creator>Mike Schmitt</dc:creator><description>&lt;p&gt;If you build the process right, there&amp;#39;s no way this can happen.&amp;nbsp; I built one of these myself once and I tested with another person where we both sat and tried to click at exactly the same time, but still one of us got into the task and the other one was locked out due to the process locking.&amp;nbsp; The process flow executes so quickly that milliseconds of difference is enough.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Appian Task</title><link>https://community.appian.com/thread/146960?ContentTypeID=1</link><pubDate>Mon, 07 Apr 2025 11:58:24 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:29a10d92-e955-4cdd-974a-11116b977a2d</guid><dc:creator>Stefan Helzle</dc:creator><description>&lt;p&gt;Do you have a specific reason to go that way? I mean, Appian processes support the idea of &amp;quot;Tasks&amp;quot; directly.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Appian Task</title><link>https://community.appian.com/thread/146959?ContentTypeID=1</link><pubDate>Mon, 07 Apr 2025 11:26:55 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:9d71eb46-14e3-4e7a-a6e4-ff652f3cb75e</guid><dc:creator>Rahul009</dc:creator><description>&lt;p&gt;Hi &amp;nbsp;,&lt;/p&gt;
&lt;p&gt;thank you for your response, but if two users click on task at the same time so they will be presented the same user input form. How to avoid this?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Appian Task</title><link>https://community.appian.com/thread/146958?ContentTypeID=1</link><pubDate>Mon, 07 Apr 2025 11:12:36 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:a2a00111-f1b5-4280-8a94-3021177da8df</guid><dc:creator>VarunTejaGurrapu</dc:creator><description>&lt;p&gt;Hi &lt;a href="/members/shubhamy3376"&gt;Rahul009&lt;/a&gt;&amp;nbsp;,&lt;br /&gt;&lt;br /&gt;I have a solution for this, please follow below steps :&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li class="" data-start="1357" data-end="1386"&gt;
&lt;p class="" data-start="1360" data-end="1386"&gt;&lt;strong data-start="1360" data-end="1384"&gt;User clicks the link&lt;/strong&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li class="" data-start="1387" data-end="1417"&gt;
&lt;p class="" data-start="1390" data-end="1417"&gt;&lt;strong data-start="1390" data-end="1415"&gt;Start a process model&lt;/strong&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li class="" data-start="1418" data-end="1630"&gt;
&lt;p class="" data-start="1421" data-end="1450"&gt;&lt;strong&gt;Checks if the task is already assigned&lt;/strong&gt; :&lt;/p&gt;
&lt;ul data-start="1454" data-end="1630"&gt;
&lt;li class="" data-start="1454" data-end="1482"&gt;
&lt;p class="" data-start="1456" data-end="1482"&gt;If Yes &amp;rarr; show user &amp;ldquo;Task already assigned&amp;rdquo; or end process.&lt;/p&gt;
&lt;/li&gt;
&lt;li class="" data-start="1454" data-end="1482"&gt;If No -&amp;gt; Change&amp;nbsp;the&amp;nbsp;&lt;strong&gt;&lt;code data-start="1675" data-end="1688"&gt;assigned_to&lt;/code&gt;&lt;/strong&gt; to the process initiator&amp;nbsp;&lt;strong&gt;&lt;code data-start="1675" data-end="1688"&gt;.&amp;nbsp;&amp;nbsp;&lt;/code&gt;&lt;/strong&gt;&lt;strong&gt;&lt;br /&gt;&lt;/strong&gt;&lt;/li&gt;
&lt;li class="" data-start="1486" data-end="1521"&gt;
&lt;p class="" data-start="1488" data-end="1521"&gt;Check if the assignment succeeded.&lt;/p&gt;
&lt;/li&gt;
&lt;li class="" data-start="1525" data-end="1568"&gt;
&lt;p class="" data-start="1527" data-end="1568"&gt;Move forward and assign the task.&lt;/p&gt;
&lt;p class="" data-start="1574" data-end="1630"&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Note :&amp;nbsp;&lt;/p&gt;
&lt;ul&gt;
&lt;li class="" data-start="1659" data-end="1716"&gt;
&lt;p class="" data-start="1661" data-end="1716"&gt;Make sure the &lt;strong&gt;&lt;code data-start="1675" data-end="1688"&gt;assigned_to&lt;/code&gt;&lt;/strong&gt; column is &lt;strong&gt;&lt;code data-start="1699" data-end="1705"&gt;NULL&lt;/code&gt;&lt;/strong&gt; by default.&lt;/p&gt;
&lt;/li&gt;
&lt;li class="" data-start="1717" data-end="1818"&gt;
&lt;p class="" data-start="1719" data-end="1818"&gt;Consider placing a &lt;strong data-start="1738" data-end="1759"&gt;unique constraint&lt;/strong&gt; on &lt;strong&gt;&lt;code data-start="1763" data-end="1772"&gt;task_id&lt;/code&gt;&lt;/strong&gt; + &lt;strong&gt;&lt;code data-start="1775" data-end="1788"&gt;assigned_to&lt;/code&gt;&lt;/strong&gt; if you want stricter DB rules.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Hope this helps you!!!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>