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. Maybe a manager has to sign to if e.g. just 2 out of 4 that
have to sign agree and there is a stand-off. He also 'just signs' but it is part
of a flow.
|
| Can you explain to me why you need identical tasks in sequence? What is the relation
between them? I get the feeling you need to start thinking out of the box and also take
into account that current real-life processes *should not* be modelled as-is
electronically. Always take business process redesign into account
|
in my understanding, co-signing maybe is that, in a tasknode, several same tasks are
delivered paralel automatically to several person, tasknode will finish if all/one
of/majority of person(s) agree/disagree.
why i need serialization or parallel same tasks is because in our system, one step of
process will be approved by several person with sequence, 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?
Thanks for your 2 link, i will read it and hopefully get useful information.
anonymous wrote :
| anonymous wrote : I read ForEachForkAH example from Wiki, i am a little confused about
that. It seems to create several node in parallel, not tasknode, so is different to
co-sign. right?
| Learn jBPM a little more in the basics... you can put anything in there, tasknodes,
subprocesses.... you name it...
I read JBPM doc, but i cant get any useful stuff in such situation.
Could you tell me more?
Thanks a lot!
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4197275#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...