What happens here is that in the start task you have a swimelane defined. I
think what happens is that the swimlane get's overridden with the actor that
started the process. Probably if you leave out the swimlane in the start-task
it will work. Not sure if it is a bug or works as designed. You
anonymous wrote : i get the message the task has been assigned to null,null
known issue with the 3.1.x webapp
The other issue I do not know about. Could be that the default behaviour in 3.1
is that the start task is assigned to the process initiator.
View the original post :
hi,
thanks for the quick reply Ronald
the 1st error is not much of a concern.
but at least the second error(i think its a very serious error)
how can a process TASK be assigned to any random user when there is a
particular swimlane(user) assigned to the Task.
one of the two Tasks after the
