nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Assignee not nulled when boundary timer event called

thysmichels

I have a process with a boundary timer event. When the timer is called it goes to the start of the process. My timer event works and gets trigger. The human task the timer event is on has a assignee (john) set.

I expect that when the timer event get's called and Cancel activity = true the task moves to the beginning of the flow and assignee is set to null. What is happening is the task is moved to the beginning of the flow but the assignee stays (john) as previously set.

How would l be able to null the assignee?

Find more posts tagged with

Comments

jbarrez

> What is happening is the task is moved to the beginning of the flow

I don't follow what you mean by this? If a task is cancelled, it is removed.

How do you do the assignment? Through a variable?

A process would help here to understand.

thysmichels

Sorry for the confusion. Here is a detailed description:
I have a human task with assignee="John" with a timer boundary event time duration PT20S which has Cancel Activity=true;. If duration expires move to the start of the process.

After 20 sec the task moves to the start but the assignee is still assigned to "John"? Should assignee=null?

Assignment is not done through variables but Activiti assignee field.

Hope that makes sense.

frederikherema1

I presume your start-event fill flow into the same user-task again? When the boundary-event is fired, the user task is deleted from the database. In case the process arrives at the same user task again, it will create a NEW Task entity, with all fields initialised based on what is defined in the bpmn20.xml. So it applies the activiti:assignee to the new task-instance.

If you want to have the task assigned to someone else, I suggest using an expression that uses a variables, which is different AFTER the boundary-event fired as opposed to the default (normal starting of a process), eg:

<br>activiti:assignee="${isTimerFired ? 'John' : null}"<br>