Home > Forum > General > Task assignment bugged?

Task assignment bugged?

0

05.10.2022

09:32

Hi,
I've got the following problem. I'm currently working on an workflow and the task assignment is not reseting it self after clicking on a path.
Meaning that all previously assigned people still have the task and even when I let all fields of the task assignment empty the task will still be given to all previously assigned Users.
Is this a bug or am I doing something wrong?
I've attached an image of my task creation and I'm using the wait for supworkflow step if that helps.

Thanks in advance
Nick

05.10.2022

10:16

Hi Nick,

I remember this behavior from an old version that tasks assigned in a wait for sub workflow step wont be cancelled on path transition. This was confirmed and I think it was fixed. Unfortunately I don't remember in which version I noticed this maybe 2020.

Best regards,
Daniel

Solution (0)

Helpful (0)

Wrong answer (0)

05.10.2022

10:26

In reply to: Daniel Krüger (Cosmo Consult)

Hi Daniel,

Im using a 2022 version. Do you know any workarounds or do I just have to deal with it?

Thanks in advance
Nick Trögel

Solution (0)

Helpful (0)

Wrong answer (0)

05.10.2022

10:31

In reply to: Nick Troegel

Hi Daniel,

Im using a 2022 version. Do you know any workarounds or do I just have to deal with it?

Thanks in advance
Nick Trögel

We used an "dummy step" which is not displayed in the status panel or diagram. From the sub workflow step a path led to this dummy step has a timeout which is set to "immediately". The real path was then moved to the dummy step.

So it looked like

Sub workflow step -> Close existing task path -> Close existing task path -> Continue with your work path

Best regards,
Daniel

Solution (0)

Helpful (0)

Wrong answer (0)

05.10.2022

11:00

In reply to: Daniel Krüger (Cosmo Consult)

The wait for subworkflow step seems to have nothing to do with it. I exchanged the subworkflow step with a system step and the same problem occured.

Thank you regardless
Nick

Solution (0)

Helpful (0)

Wrong answer (0)

05.10.2022

11:27

In reply to: Nick Troegel

The wait for subworkflow step seems to have nothing to do with it. I exchanged the subworkflow step with a system step and the same problem occured.

Thank you regardless
Nick

Hi Nick,

it could also be that it was a system step where I noticed this. I only remember the described issue, that I created a support ticket or user voice and how the workaround was.

Best regards,
Daniel

Solution (0)

Helpful (0)

Wrong answer (0)