[Jboss-dev-forums] [Design of JBoss jBPM] - Re: Two Transition Definitions

[hosierdm <do-...@jb...>]

I think I understand your concerns, and they make sense.  Unfortunately, I'=
m not really hip to the concept of guards on transitions as you describe it=
, so that discussion is a bit over my head. =20

Here is an example where I thought conditions on transitions in general cou=
ld be useful.  My company has written a framework for a customer that inclu=
des workflow using jBPM.  Part of that framework includes some sub-processe=
s that provide the customer with some built-in functionality.  One of these=
 sub-processes logs into a network device, runs some commands, and then set=
s an exit code process variable.  To determine what their process should do=
 next, the customer was having to continually add Decision nodes to their p=
rocesses to test this exit code and transition to an error state or whateve=
r.  So I got to thinking it would be nice, for example, to be able to speci=
fy conditions on transitions coming out of a process state.  Maybe I led th=
e customer astray and there is an easier way, but I didn't see any way to f=
igure out the "status" of the sub-process and change the process path of ex=
ecution without adding a node.  Basically, what it boils down to is the des=
ire to have as few nodes and transitions in a process as is possible, in or=
der to keep the process clean and simple.

Obviously you have a bigger picture view of jBPM, so this whole concept cou=
ld be complete bunk.  Hopefully my use case helps clarify my thought proces=
s though.

View the original post : http://www.jboss.com/index.html?module=3Dbb&op=3Dv=
iewtopic&p=3D3953756#3953756

Reply to the post : http://www.jboss.com/index.html?module=3Dbb&op=3Dpostin=
g&mode=3Dreply&p=3D3953756