-
1. Re: Suggestion for transitions
mwohlf Jun 29, 2010 6:13 AM (in response to jochen_mader)Can you maybe give an example, I don't really understand.
"allow JUEL scripts for transition names"
would this mean you have transition like this in your process definition:
<transition name="#{someObject.resolvedTransition}" to="nextActivity" />
-
2. Re: Suggestion for transitions
jochen_mader Jun 29, 2010 6:57 AM (in response to mwohlf)Yep, that would be my suggestion.
And while we are at it we could enable users to prvoide additional ELResolvers
-
3. Re: Suggestion for transitions
mwohlf Jun 29, 2010 7:08 AM (in response to jochen_mader)Jochen Mader wrote:
Yep, that would be my suggestion.
And while we are at it we could enable users to prvoide additional ELResolvers
+1 from me for the ELResolvers, the first thing i would resolve would be the #{authenticatedUser} it's a PITA to get this information somehow in jBPM
as for the transition ,
whats the advantage of having EL in transition names compared to using a decision?
http://docs.jboss.com/jbpm/v4/userguide/html_single/#decision
-
4. Re: Suggestion for transitions
jochen_mader Jun 29, 2010 8:33 AM (in response to mwohlf)I want to be able to signal the transition.
Example:
There is one user who does a couple of changes on a data item, he then either "submits" (signal execution with the string "submit") or saves the data item.
When he "submits", another user will be able to "accept", "decline" or "defer" the changes with each signal triggering a different workflow.
A decision for me involves some computation which has to be done inside jBPM whereas what I am doing is that a user actively triggers the different workflows.
So I would say that using signalExecution is the correct way in a process sense.
Thanks,
Jochen