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, if the user after accepting the task, reassigns it to another user or rejects it then, whoever accepted this task needs to be updated in that db field.
We can store tp!owner details in a process variable once the task is submitted. However, we want it to be stored before the task submission.
I created an expression rule which calls a!queryProcessAnalytics() to get tp!owner and tried using it in rule event.
Rule event is checking, if tp!owner is not null then a db write is done. However, my process is getting paused. I don't understand why the expression rule haivng a!queryProcessAnalytics() is not getting evaluated in rule event?
Is there any other way to implement this scenario.
Discussion posts and replies are publicly visible
Hi diptis ,
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.
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 issuerefer this queryProcessAnalytics function is not working in rule event?