What makes User Tasks between Workflows Contiguous... or Not?
Hey all,
Can anyone help me understand technically why or when user tasks for the same user between two global workflows become non-contiguous?
Thanks,
Tom
Tom Friesen
Posted 4 years ago · Edited 1 year ago·Last reply 4 years ago
3 comments
alvinuseree
·4 years ago · Edited@tom.friesen What an interesting problem I have zero idea if the below will be helpful but …
Do you think maybe it’s the End event before the next User Task that is the issue i.e.
Would maybe redesigning the workflow to allow for recursive execution of call activities work? I guess this way the next User Task is started before the previous workflow ends i.e.
Alexandra Jorgenson
Admin4 years ago · Edited@tom.friesen One of our engineers wanted to help but had these questions: " I don’t fully understand the question. If we have 2 global workflows, those workflows are completely independent. Both can have user tasks assigned to the same user but there is no correction between them. Can Tom provide more details?"
arthurburkhardt
·4 years ago · EditedIf I understood correctly, the problem is: if given a global workflow A, calling another workflow B with a call activity. The first time, the pop-up of workflow B appears correctly, but not the second time.
See also: Workflow, Called Workflow User Task Continuity -
Developers - The Data Citizens Community (collibra.com)
I have no idea why it would have that behavior.
Is my understanding correct, @tom.friesen?