Hello to all, I have an activity A that is assigned to a group of use

Hello to all,

I have an activity A that is assigned to a group of users.

In an instance of the process a task corresponding to activity A is generated and is assigned to that group of usres. Then one of the users in the group actually clicks the accept button and starts working on the task. Finally at some time the user finishes the task corresponding to the activity.

Is there some way to record in a process variable
a) the user that actually finished the task corresponding to activity A (not the group name that the task was assigned to)?
b) the time the user actually clicked the accept button to start working on the activity?

I have a subsequent activity B in the process where I want this information is recorded in a reporting database.

Thanks in advance,

Nikos

OriginalPostID-163845

OriginalPostID-163845

  Discussion posts and replies are publicly visible

Parents
  • @nikolaosm To answer your question much clearly (b in particular),

    Is there some way to record in a process variable

    a) the user that actually finished the task corresponding to activity A (not the group name that the task was assigned to)?
    As already said by others, tp!owner is the attribute that holds the user who has accepted or completed the task. Further I would like to suggest to go through documentation at https://forum.appian.com/suite/help/7.10/Process_and_Report_Data.html and https://forum.appian.com/suite/help/7.10/Process_and_Report_Data.html#Task_Properties in particular.

    b) the time the user actually clicked the accept button to start working on the activity?
    Actually there isn't a way to capture the task properties (tp!assignees, tp!owner etc) or activity class parameters etc into process variable without completion of the corresponding user input task. So you need to wait until the completion of node in order to save the tp!owner into PV eventhough the tp!owner is populated immediately when the user or user in the group accepts the task(Reference: https://forum.appian.com/suite/help/7.10/Process_and_Report_Data.html#Task_Properties). Perhaps not the best, but the only way to say that the task has been started working on by is to poll the analytics at regular interval and check for existence of tp!owner attribute for the corresponding process and its task. Once if the polling has come back with the desired results, we can start making use of them to update any object(could be PVs in any process or a table in the database).
Reply
  • @nikolaosm To answer your question much clearly (b in particular),

    Is there some way to record in a process variable

    a) the user that actually finished the task corresponding to activity A (not the group name that the task was assigned to)?
    As already said by others, tp!owner is the attribute that holds the user who has accepted or completed the task. Further I would like to suggest to go through documentation at https://forum.appian.com/suite/help/7.10/Process_and_Report_Data.html and https://forum.appian.com/suite/help/7.10/Process_and_Report_Data.html#Task_Properties in particular.

    b) the time the user actually clicked the accept button to start working on the activity?
    Actually there isn't a way to capture the task properties (tp!assignees, tp!owner etc) or activity class parameters etc into process variable without completion of the corresponding user input task. So you need to wait until the completion of node in order to save the tp!owner into PV eventhough the tp!owner is populated immediately when the user or user in the group accepts the task(Reference: https://forum.appian.com/suite/help/7.10/Process_and_Report_Data.html#Task_Properties). Perhaps not the best, but the only way to say that the task has been started working on by is to poll the analytics at regular interval and check for existence of tp!owner attribute for the corresponding process and its task. Once if the polling has come back with the desired results, we can start making use of them to update any object(could be PVs in any process or a table in the database).
Children
No Data