Paul,
I'm in doubt on what to advise you. On the one hand what you describe to me
sounds as essential for the process and should be modelled in. On the other
hand, I understand your reluctance and to some extend agree.
Ok now a more concrete response...
What you could do is create a task-node
Sorry about that...I definitely see how explaining why normal paths like
building it into the process definition aren't a possibility would help people
that are kind enough to help me... and hopefully others who might be searching
for answers later.
To answer your questions...
anonymous wrote :
Hundereds of tasks? Wow what kind of branch is that?
First of all, it would be nice if in further posts you also describe what has
been proposed and 'shot down'. Saves me an initial post and writing these kinds
of second posts.
What is a "workflow managers"? A kind of admin? Give him the jB
It's not an option that our user community would accept (i.e. the option you
suggest has been posed and shot down as the skip feature is already possible in
our current workflow engine).
Customer's workflows typically have hundreds of tasks any of which workflow
managers can elect to "skip".
put a decision in front of it and decide there way more visible
(graphically)
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4229528#4229528
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4229528
