-
1. Re:
sebastian.s Oct 8, 2009 4:15 AM (in response to krohm)AFAIK is jBPM lacking a permission system to restrict users from starting processes at the moment so every user can start every process right now.
-
2. Re:
krohm Oct 8, 2009 4:21 AM (in response to krohm)Thanks.
That's what I was suspecting anyway :) -
3. Re:
krohm Oct 8, 2009 4:33 AM (in response to krohm)And an additional question on the same subjet ...
I did not manage to "capture" the user that started the process in a swimlane. (in order to allow this user perform other tasks afterwards).
Is this also impossible ?
I've seens several references to an "initiator" swimlane, but I haven't managed to make it work. -
4. Re:
kukeltje Oct 8, 2009 5:10 PM (in response to krohm)the initiator swimlane is something from jBPM 3
-
5. Re:
krohm Oct 9, 2009 3:39 AM (in response to krohm)Ok.
Is there a way to "capture" the initiator in JBPM4 ?
I mean getting the Id of the user that initiated the process.
It is not something unusual that this user has a separate swimlane. -
6. Re:
gfargone Oct 9, 2009 12:49 PM (in response to krohm)"Krohm" wrote:
Ok.
Is there a way to "capture" the initiator in JBPM4 ?
I mean getting the Id of the user that initiated the process.
It is not something unusual that this user has a separate swimlane.
I just store it in the process context. I have a web form that gathers information, creates the a process instance, and stores a couple of other things in the context as well. -
7. Re:
kukeltje Oct 9, 2009 12:59 PM (in response to krohm)That is indeed an option. You can also set the actor of the swimlane of that specific task.