Assignment Listener in Camunda 8

[BerndVarga]

I currently evaluate to move our Camunda usage from Camunda 7 to Camunda 8.

In our current implementation we use nearly on each user task an assignment listener. In the listener implementation (which can be process dependent) we validate the user change and store the changed user key for further usage.

Is there an option to react on the assignment change in Camunda 8?

I have read following post:

Task listeners and Execution Listeners in Camunda 8

Hi Team, What are the alternate ways to achieve the requirements for task listeners in Camunda 8? For Eg, when a user task reaches time out, I need to notify someone or reassign task to someone else. Earlier in Camunda 7, there were events like create ,assignment, delete, timeout etc where at any of this stage we could configure listener. How can I achieve the same using Camunda 8? Even if we use a service task and write a worker, how can I meet my requirement at each of the task stages ment…

Are there plans to add such capability in the future?

BR Bernd

[Philipp_Ossler]

Hi @BerndVarga,

thank you for raising this up.

Currently, the user task assignment is not handled inside Zeebe. All user tasks are handled by Camunda Tasklist.

Would it help you if Camunda Tasklist would provide a listener? For example, in the form of a GraphQL subscription?

Best regards,
Philipp

cc: @felix-mueller

[BerndVarga]

Hi @Philipp_Ossler ,

thanks for your response.

In the meantime I have an other view on that topic. In our case we can cover that requirements on our own tasklist service and process service level to handle the assignment changes there.

But for sure we have no entry point, if the assignee was changed outside of our stack. This with GraphQL subscription can fix it, but current I don’t see it as a high prio topic.

BR Bernd

[skayliu]

@Philipp_Ossler @BerndVarga I think there is a way, according to this, zeebe-script-worker , the assignment can be defined as a expression , and when the ScriptJobHandler run, we can get the result and pass the variable back, then we get the assignment user.

[BerndVarga]

But this will run only once in the creation phase of the user task, or?

[jwulf]

Yes. Unless you have an implementation of the user task worker that exposes lifecycle changes via notification, the only notification you could get is async.

You could model it with a script worker for assignment of the task, then an incoming message for the task completion (and even for assignment / assignment change). However, you lose the semantics of user task in the model.

Josh