<?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>Need to get tp!owner and to save in Database field once the user accepts a task but has not submitted the task yet.</title><link>https://community.appian.com/discussions/f/general/12612/need-to-get-tp-owner-and-to-save-in-database-field-once-the-user-accepts-a-task-but-has-not-submitted-the-task-yet</link><description>There is a scenario where we need to identify who is currently working on the task. So, the user who accepts the task needs to be captured before the task completion. The user who accepts the task (i.e tp!owner) needs to be stored in a db field. Also</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Need to get tp!owner and to save in Database field once the user accepts a task but has not submitted the task yet.</title><link>https://community.appian.com/thread/56260?ContentTypeID=1</link><pubDate>Wed, 06 Jun 2018 06:41:13 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:e0f9e53b-48fd-47a4-833b-b441d2d92116</guid><dc:creator>diptis</dc:creator><description>Thanks Shubham!&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Need to get tp!owner and to save in Database field once the user accepts a task but has not submitted the task yet.</title><link>https://community.appian.com/thread/56259?ContentTypeID=1</link><pubDate>Wed, 06 Jun 2018 06:35:11 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:72970666-b1d1-4bbf-bc45-d8fce74d1a53</guid><dc:creator>Shubham Aware</dc:creator><description>&lt;p&gt;Hi diptis ,&lt;/p&gt;
&lt;p&gt;Actually i also had a same kind of scenario where i need to find tp!owner before the task completion for that i have tried through a!queryProcessAnalytics() function inside rule event and also in escalation, But it will paused your process and status changed to paused by exception.&lt;/p&gt;
&lt;p&gt;I will suggest you to use timer event which will find tp!owner in script task after some fixed interval of time. Use long interval of time to avoid 1000 node instance issue&lt;br /&gt;&lt;br /&gt;refer this&amp;nbsp;&lt;a href="/discussions/f/general/12527/why-queryprocessanalytics-function-is-not-working-in-rule-event"&gt;queryProcessAnalytics function is not working in rule event?&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Need to get tp!owner and to save in Database field once the user accepts a task but has not submitted the task yet.</title><link>https://community.appian.com/thread/56258?ContentTypeID=1</link><pubDate>Wed, 06 Jun 2018 06:23:13 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:99d853a9-cac6-4da4-a0e6-2e14ef188d32</guid><dc:creator>diptis</dc:creator><description>Thanks Parag.&lt;br /&gt;
This is a good approach and I think I need to use a timer which checks periodically for tp!owner to be  not null. Using timer will effect the performace.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Need to get tp!owner and to save in Database field once the user accepts a task but has not submitted the task yet.</title><link>https://community.appian.com/thread/56257?ContentTypeID=1</link><pubDate>Wed, 06 Jun 2018 06:04:41 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:56cf09b4-06eb-4ef5-9899-d4253520fac8</guid><dc:creator>diptis</dc:creator><description>Thanks Ashvin, Getting details from task report is a better idea. However, the client don&amp;#39;t want a new report to be created. He wants that the user who accepted the task (but has yet not submitted it) needs to be displayed in existing records. The records present in our application are entity backed record.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Need to get tp!owner and to save in Database field once the user accepts a task but has not submitted the task yet.</title><link>https://community.appian.com/thread/56233?ContentTypeID=1</link><pubDate>Tue, 05 Jun 2018 17:03:33 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:d80bb14e-6523-4b9d-8601-3977e89e9385</guid><dc:creator>paragk998</dc:creator><description>Hi&lt;br /&gt;
Get task id by task name from process properties&lt;br /&gt;
Based on that get the status of task&lt;br /&gt;
And tp!owner&lt;br /&gt;
If status is assigned and tp!owner =null&lt;br /&gt;
Task assigned but not accepted&lt;br /&gt;
If status is accepted and tp!owner have value&lt;br /&gt;
Task is accepted save value in db&lt;br /&gt;
You need to track this in parallel flow &lt;br /&gt;
Which will continuously monitor your task in running process.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Need to get tp!owner and to save in Database field once the user accepts a task but has not submitted the task yet.</title><link>https://community.appian.com/thread/56228?ContentTypeID=1</link><pubDate>Tue, 05 Jun 2018 15:16:12 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:e9496027-60b2-4395-9024-e268a42533dd</guid><dc:creator>Ashvin Kapur</dc:creator><description>Additionally, search existing discussions for this topic, as there seem to be several related discussions which can provide additional details.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Need to get tp!owner and to save in Database field once the user accepts a task but has not submitted the task yet.</title><link>https://community.appian.com/thread/56227?ContentTypeID=1</link><pubDate>Tue, 05 Jun 2018 15:13:36 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:57f0810b-5508-4f65-8ad5-088fdab0e8d7</guid><dc:creator>Ashvin Kapur</dc:creator><description>My suggestion would be to identify the user who accepted the task via a task/process report as opposed to holding the value in the DB. You should be able to meet your reporting requirements using the task/process report model instead of entity backed.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>