Hello, I am on Appian version 7.8. I have a tempo report i

tapans over 8 years ago

Hello,

I am on Appian version 7.8.

I have a tempo report in which one grid column is fetching task acceptance time from one portal report. In the portal report, I am using this condition to get the acceptance time : =if( task_status() = 0, null, task_assignment_time() + Lag())

My scenario in which I am getting wrong acceptance time :
- I have accepted one task at 4:00 PM
- As per the business need, I have reassigned that task to team mate Tom at 4:15 PM
- Tom has accepted the task at 4:30 PM

So in the tempo report, acceptance time should display 4:30 PM but in place of that it is displaying 5 PM (adding 30 minutes more from first acceptance). getTaskAcceptedTimestamp function is not working in portal.

Could any one please suggest me any alternative I can apply in portal to get accurate task acceptance time?
Please let me know if any additional detail is requited.

Thanks!

Discussion posts and replies are publicly visible

0 davidm415 over 8 years ago

Lag() seems to take the very first assignment time for a given task and in your formula adds it to the most recently assigned time for that task. This seems to work fine when a task is not reassigned. However it can create some strange scenarios when a task is reassigned. Taking a task originally assigned 10 days ago and reassigning it to another user would give you a task acceptance time of 10 days into the future. Depending on your use case, the process start time from the task metrics list might be more accurate.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 sikhivahans over 8 years ago

@tapans Hi, It might be worth trying the following expression for calculating lag time instead of depending on Lag() task metric: totime(fn!now() - task_assignment_time())

Also you mentioned that getTaskAcceptedTimestamp function is not working in portal. True, some expression rules or functions won't be available in the report and afaik this is also mentioned in the documentation. Well I couldn't pick up the link at this moment, but will let you know for sure when I find it.

If you still determined to use getTaskAcceptedTimestamp, you could adapt the following approach:
Step - 1: Get the process analytics datasubset. Make sure that task id is present in the resultant datasubset.
Step - 2: Invoke the getTaskAcceptedTimestamp function for each and every record found in the datasubset obtained in Step - 1 by making use of corresponding task id. Join this data with the data obtained in Step - 1.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 sikhivahans over 8 years ago

@tapans Excuse for the type - *If you are still determined
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 sikhivahans over 8 years ago

Added to above, Looping Functions, Scripting Functions, Evaluation Functions aren't available in Portal reports. (Reference: forum.appian.com/.../Appian_Functions.html). And getTaskAcceptedTimestamp falls under Scripting Functions category.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 tapans over 8 years ago

Hello sikhivahans,

Than you so much. I have used getTaskAcceptedTimestamp in tempo catching task ID from portal and it resolved my concern.

Have a great day!
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 sikhivahans over 8 years ago

@tapans That's great. My pleasure.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel