Hi Christian.
Let me quickly comment on this – from a BPMN & best practice perspective I would never use the pattern Oracle describes here but always use a form defined on the start event. As the process instance should not get kicked off until the form is completed this is the only way to model that correctly in BPMN. As soon as you have a UserTask this can only be active after the process instance has started – everything else is not valid BPMN – and hence not a good workaround. You could even think of extension attributes you can set on the start event (or maybe use the lane the event is placed in ) for defining who is allowed to start the process instance – however, this is not a build in feature camunda provides (but can be added in a project specific way).
Cheers
Bernd
--
You received this message because you are subscribed to the Google Groups "camunda BPM users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to camunda-bpm-us...@googlegroups.com.
To post to this group, send email to camunda-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/camunda-bpm-users/5df59b64-3f12-493f-bf00-1f6b32eed20d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hi Christian.
From a BPMN spec perspective c lanes do not have a fixed execution semantics – so I don’t see a problem of using them for adding information to a start event.
Cheers
Bernd
To view this discussion on the web visit https://groups.google.com/d/msgid/camunda-bpm-users/e658e74a-913c-4b0e-8738-02891da7f6b8%40googlegroups.com.
I like the view on „Lane driven“ vs. “activity driven”. We see also another advantage of not using lanes: Almost all process models get more compact and easier to read – as the lanes force you to use a lot of space and sometimes very long sequence flows…
To view this discussion on the web visit https://groups.google.com/d/msgid/camunda-bpm-users/75beceff-757b-422f-bf56-81d37f49cb35%40googlegroups.com.