I got a problem with my workflow,I'm using a substitution criteria and when the swimlane is reinitialised the task is send to the previous actor assign to the swimlane
I will try to explain more correctly.
I got a task with a swimlane define as this:
ru.runa.af.organizationfunction.ExecutorByNameFunction(developpeur);ru.runa.af.organizationfunction.ExecutorByNameFunction(manager):alfea.TimeoutSubstitutionCriteria(${idProcess},${idSwimlane},3,${user2},${user})
and as my workflow make loop if the developper accept or refuse the task, the swimlane developpeur could have differents actor assign to it
and the problem is that when the process enter that loop and that a new actor is define in replacement the task is send to the previous actor instead of the new one.
where it could come from?
Hope you understand me, it's not easy to explain
Regards,
Bubble
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I got a swimlane with this initialisator :
ru.runa.af.organizationfunction.ExecutorByNameFunction(developpeur);ru.runa.af.organizationfunction.ExecutorByNameFunction(manager):alfea.TimeoutSubstitutionCriteria(${idProcess},${idSwimlane},3,${user2},${user})
the first time I pass on the state all work fine
but if in that state the actor refuse the task the workflow has to go one step back and the swimlane developpeur as a new actor choose by the manager
the swimlane developpeur is reinitialized correctly but the substituable swinlane keep the old actor
Don't understand why
Regards,
Bubble
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I got a problem with my workflow,I'm using a substitution criteria and when the swimlane is reinitialised the task is send to the previous actor assign to the swimlane
I will try to explain more correctly.
I got a task with a swimlane define as this:
ru.runa.af.organizationfunction.ExecutorByNameFunction(developpeur);ru.runa.af.organizationfunction.ExecutorByNameFunction(manager):alfea.TimeoutSubstitutionCriteria(${idProcess},${idSwimlane},3,${user2},${user})
and as my workflow make loop if the developper accept or refuse the task, the swimlane developpeur could have differents actor assign to it
and the problem is that when the process enter that loop and that a new actor is define in replacement the task is send to the previous actor instead of the new one.
where it could come from?
Hope you understand me, it's not easy to explain
Regards,
Bubble
Hi,
How do you replace swimlane executor code?
Are you sure the new actor code was placed into swimlane variable in the loop?
Regards,
Vitaliy S
I got a swimlane with this initialisator :
ru.runa.af.organizationfunction.ExecutorByNameFunction(developpeur);ru.runa.af.organizationfunction.ExecutorByNameFunction(manager):alfea.TimeoutSubstitutionCriteria(${idProcess},${idSwimlane},3,${user2},${user})
the first time I pass on the state all work fine
but if in that state the actor refuse the task the workflow has to go one step back and the swimlane developpeur as a new actor choose by the manager
the swimlane developpeur is reinitialized correctly but the substituable swinlane keep the old actor
Don't understand why
Regards,
Bubble