Mehmet Salgar [http://community.jboss.org/people/speleomaniac] created the discussion "Re: Swimlanes and Task Assignements" To view the discussion, visit: http://community.jboss.org/message/561771#561771 -------------------------------------------------------------- Naturally I read the document but I can say that it is not behaving like it is there described, at least not with jbpm console For ex... h2. '11.7. Swimlane in start task A swimlane can be associated with the start task to capture the process initiator. A task can be specified in a start-state. That task be associated with a swimlane. When a new task instance is created for such a task, the current authenticated actor will be captured with http://docs.jboss.com/jbpm/v3/userguide/security.html#authentication Authentication.getAuthenticatedActorId() and that actor will be stored in the swimlane of the start task.' That is definitely not happening, the group that I defined for the swimming lane is assigned to the task as ActorPool but Task is not assigned to the actually authenticated user, I have to do that manually.... To make the thing worse, I can assign an actor that is not belonging to the group defined in the swimlane and jbpm doesn't complain about that also.... -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/561771#561771] Start a new discussion in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]