Capture user who accepts a task

RE: Capture user who accepts a task

mohanp — Thu, 18 Aug 2016 09:11:36 GMT

*Please read "Anyone of the component" as the component where we are using a!save() function.

RE: Capture user who accepts a task

mohanp — Thu, 18 Aug 2016 08:58:42 GMT

Thanks Narasimhaadityac, Yes, I understand your solution but in your case user has to interact with any one of the component in the form, else process won't be trigger. Say user has accepted the task and navigate to the other tab as he may want to complete this task on later time. Any idea by which we can trigger a process without interacting with the form field?

RE: Capture user who accepts a task

narasimhaadityac — Thu, 18 Aug 2016 07:09:23 GMT

Hi Mohan, we did tried one way in 7.11, as mentioned in above post when the task is accepted by the user, tp!owner would be populated and the form is reloaded. what we have done we used the fn!startprocesswrite with bind variables and then invoking a sub process on the first editable fields saveInto and passing the tp!owner as the input so that the information would be written to the database.

RE: Capture user who accepts a task

aayusha — Thu, 18 Aug 2016 06:54:47 GMT

I am not sure, whether a!queryProcessAnalytics can be utilized in rule event or not.
AFAIK, query rules or query entity doesn't work in rule event, similarly I think the queryProcessAnalytics will not work.

RE: Capture user who accepts a task

mohanp — Thu, 18 Aug 2016 06:49:33 GMT

Thanks aayusha, We are on version 16.1 and I think a!writeToDataStoreEntity() is available from 16.2 onwords. Attached is a rule which returns true if task has been accepted and I'm calling this rule on rule event inside a process and based on this rule condition I'm trying to write status into DB. When am calling this rule in script task it's returns valid Boolean value but when I call it into rule event my process goes into Paused mode and I got error alert "ERROR:EVAL:@reason=index" Such errors occur if we use with or load inside the rule but I am not using with or load in my rule.

Identify Task Status.txt

RE: Capture user who accepts a task

aayusha — Thu, 18 Aug 2016 05:57:52 GMT

@mohanp, try using a!queryProcessAnalyatics in the load(), whether the task has been accepted or not, once you know that the task has been accepted, you can use a!writeToDataStoreEntity() to save that detail to database.
You may to take care of case when the user reopens the same task after accepting once.

RE: Capture user who accepts a task

mohanp — Thu, 18 Aug 2016 05:39:18 GMT

Hi Aayush, I want to identify the accept click on the form (OOTB Accept option). As soon as user accept the task I need to trigger a process which will write task status as Accepted into DB. Any idea how to capture Accept event?

RE: Capture user who accepts a task

bhaktit — Wed, 14 Jan 2015 08:08:44 GMT

Thanks rajivr

RE: Capture user who accepts a task

Rajiv Rahul — Tue, 13 Jan 2015 17:28:01 GMT

Hi Bhaktit,
There is no other way but to use 'Task report by Process Model' and use the 'Execute Process Report' smart service(under Analytics) to pull the data from the task report. Using above you can track the status of users who were assigned that task.

Note: In above task report, you can edit the 'From column' to tp!owner(which is pp!initiator by default) or add a new column(as tp!owner) so that you can track the person who has accepted, completed etc..

RE: Capture user who accepts a task

bhaktit — Mon, 22 Dec 2014 09:04:41 GMT

hi..I have a use case where I am assigning a task to different groups and I need to capture which group has not completed that task . Can you please guide ? Thanks in advance..

RE: Capture user who accepts a task

Navajith K — Mon, 24 Mar 2014 15:50:49 GMT

Please reade "capture the name", to "capturing tp!owner"

RE: Capture user who accepts a task

Navajith K — Mon, 24 Mar 2014 15:48:57 GMT

Hi aayusha, Could you please let me know how you were able to figure this out? I tried this congiguring "Tasks by Process Model" report in Analytics node and capture the name. Please let me knw where we need to put the analytic node, before or after the user input task, If it is before then that task will not be there in the report and if it is after, the task will be completed. Your help is highly appriciated, Thank You

RE: Capture user who accepts a task

mikec — Fri, 02 Aug 2013 21:05:04 GMT

We do something similar where we have created a grid/queue where a user can go in and open a non-assigned task and then either assign it to themselves or to someone else. The department head has a grid view of all requests coming into his department and he can filter by assignee to see who is handling what assignment and which one's have not been assigned.

RE: Capture user who accepts a task

aayusha — Fri, 02 Aug 2013 20:15:51 GMT

Hi
Thanks All
If I combine suggestions from Shaun and elizabeth, then it works.

RE: Capture user who accepts a task

aayusha — Fri, 02 Aug 2013 20:07:12 GMT

Hi

As far as I have understanding that tp!owner should be saved in process variable to use further which means that i would assign tp!owner to process variable in outputs tab of Data tab in properties of user task.
But the point is output tab executes when task node is completed from user end.
May be I am not getting your answer in a right way. Can you elaborate more on that?

Thanks

RE: Capture user who accepts a task

elizabeth.epstein — Fri, 02 Aug 2013 18:25:13 GMT

tp!owner is populated as soon as a user accepts the task. So you can use tp!owner to report on what you want.

RE: Capture user who accepts a task

Shaun Kilby — Fri, 02 Aug 2013 17:55:27 GMT

I believe this depends on what you are looking to gain from identifying the assignee. A tasks report by process model might be the route you're looking for. If you need to utilize this information in process, you could use the analytics node to pull this information from the report.

RE: Capture user who accepts a task

aayusha — Fri, 02 Aug 2013 17:06:01 GMT

Is there any other solution for the problem?
Any pointers will be helpful.

RE: Capture user who accepts a task

aayusha — Fri, 02 Aug 2013 17:05:25 GMT

I understand that, solution provided above will solve the issue. But it will increase one task everytime I want to know who accepted the task.

RE: Capture user who accepts a task

shelzle — Fri, 02 Aug 2013 16:57:35 GMT

I do this by chaining two tasks. The first is the one that gets assigned and saves who klicked the submit button. The second task is the actual task.