We have a user input task assigned to a group and a user accepts the task, is there a way we can capture those task details to separate table in DB when that task is in accepted state before the task gets completed.
Discussion posts and replies are publicly visible
There is no direct way to do that. But all the task details are accessible via process reporting.
Do you have a specific use case in mind?
I'm currently using task report to get task details. I'm capturing task assigned and task completed date and time every time to db, but I need to capture when the user accepts the task as well. There is function gettaskacceptedtime() to get the date and time, but using this I can update the DB only after completing the task. My scenario is to update the DB instantly when user accepts the task. Thanks in Advance.
While there are options, I would not recommend any of them.
May I ask why that instant update is so important?
Hi Arun,
I have an approach in my mind that can work. You can start two parallel flows. 1 - To assign the task, 2 - To run a loop inside the process model that has a delay of 120 seconds. In every iteration of that loop, you query the task report to see if the task status has been changed to 'accepted'. If yes, you can break that loop. Now the value of delay can be configured depending on the use case and additional checks can be applied to stop the infinite run of the loop.
This is one of the ideas I would not want to recommend. While this works, it adds load to the system and needs to be built around each an every task.
So I would like to ask the first "Why" in the Five-Whys-Method ;-)
Agreed
In order to calculate SLA I need those details to be updated.
You mean reaction time vs solution time. So the data is there in process analytics.
Can you explain your SLA calculation procedure? And when are the results needed?
For SLA we are trying to calculate Task Accepted time vs Solution time. Also we are logs related to task details where we are not able to capture task accepted state. Because if we use process report once the process is completed and archived or deleted data will not be available right.
True.
I try to implement two kinds of reporting.
One is about the current activity in the application. This is used by the operations manager to see whether he needs to do something now. This would use a process report.
The other is about the past. This is used be the service owner to see how SLAs where met and other KPIs. He uses these numbers to improve the overall service delivery. This would use a DB report.