websale - process definition - doubts

[brittm]

A swimlane without an actor assignment does not imply any limitation as to who can perform a task or to whom a task is assigned. The swimlane only associates multiple tasks to a single named role. In the case of the websale example, the default process definition doesn't assign the 'buyer' role to anyone until a new process instance is actually started, at which point the logged in user is assigned to the 'buyer' role.

If you want to ensure that only certain individuals or groups can start a new process, you'll probably need to handle that restriction in your user interface. I believe the swimlanes/task assignments are intended only to manage a process after it has already been started.

-Britt

[kukeltje]

IT could be that in a future release jBPM will also check the roles. It did this in 2.0, but was not a major priority for 3.0

[tom.baeyens]

correct, ronald.

but FYI, i would also like to add that these checks should be built into the user interface.

the UI *must* have that knowledge anyway, or otherwise the UI starts offering command options that result in "sorry, but you are not allowed to push this button".... then why show the button ?!

if you put that verification in the process (which can be done), you always end up in a situation where you provide buttons that may not be clicked.

regards, tom.

[kukeltje]

oh, I totally agree. But in many cases (at least for the process states, tasks etc.) You can either see/execute that task or not. It is not the case that user A can only trigger transition 1 and not transition 2 on the same state , while user b can trigger both.

Ronald