anonymous wrote :
| Because what you want to do is dirty, uncommon, error-prone, hides 'flow'
in javacode etc But I was not talking about this specific co-signing thing,
I was talking about the fact that you could not see you could place a
subprocess or something else in the
sorry, no... well, I could , but do not want to spend the time on it. If this
is to complicated for you (it is much simpler than what you were trying to
achieve), I am afraid many more questions will come out of it. Remember... this
is my FREE time, I'm not a JBoss employee or trainer or
anonymous wrote : but what they do are almost same. so i want to do it in one
task-node, as co-signing does. If difficult to implement, i will change it to
one person one task-node. Is it the correct way?
Again... you say you *want* it, but what is the process requirement...AND you
say
anonymous wrote : co-signing is creating serverl tasks in one tasknode, but
runing order of them are specific.
You can't as mentioned earlier
anonymous wrote : what i need is like it, except that the order can be
specified.
Again... you can't Tasks carried out one after another (if that
Thanks for you reply.
anonymous wrote :
| anonymous wrote :
| | co-signing is creating serverl tasks in one tasknode, but runing order
of them are specific.
| |
| Again... you can't Tasks carried out one after another (if that is
important) are not, never the same.. The
anonymous wrote : As you said, in this scenario, this tasks should only be
regarded as serveral tasknode instead of one tasknode, which is diffrent from
co-sign.
No, I disagree. 'Co-signing' for for me is having a set of people agree on a
businessdocument. In real life (if it is a paper
anonymous wrote :
| No, I disagree. 'Co-signing' for for me is having a set of people agree on
a businessdocument. In real life (if it is a paper document) that can only be
done in sequence. Electronically it can be done in parallel. Furthermore the
'co-signing PROCESS can be complicated.
co-signing is two different tasks in one way or another related to the same
casedata
Making the number of tasks runtime configurable is possible with the
foreachforkhandler Example is in the wiki. And searching the forum might
help... some of these questions have been asked and
co-signing is creating serverl tasks in one tasknode, but runing order of them
are specific.
what i need is like it, except that the order can be specified.
Could you give the example link to me, i could not find it, sorry.
View the original post :
i know i can model it in process.
set it configurable, not model it in process.
I aslo want to know if possible to make it like co-sign?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4196732#4196732
Reply to the post :
Model it in your process, multiple task-nodes, forks etc... otherwise you are
creating a workflow within a workflow-node which sounds bad...
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4196245#4196245
Reply to the post :
11 matches
Mail list logo
