Thank You!
Now, I also can give workitem-fields back to the Workflow and use them
to take different paths through the process-definition.
like this:
participant:
...
$i = Integer(gets)
workitem.fields['total'] = $i
end
reply_to_engine(workitem)
...
pdef:
user_3 :task => 'doing user_3 stuff...'
echo 'total was given: ${f:total}'
echo 'back from participant-implementation...'
user_4 :task => 'doing user_4 stuff now...'
But again some open questions, related to the topic:
1. It seems as if I have to handle myself which participant will be
executed by whom. Not like in my "for-klaus" example, where only the
current user can execute the participants with the same name.
2. During combining the "for-klaus" example with a self implemented
participant, I found out this is asynchronously. Means. If I am
waiting for a user-prompt within the participant-implementation, My
Input can also be an Input for the "main-command-loop" in this:
def run
loop do
print("#{@user}" + (@workitem ? ":#{@workitem.fei.sid}" : '') +
'> ')
self.eval(gets)
end
end
Is there a way to handle the Participant-Implementation in an other
terminal (later I would generate some web-output instead)
3. If I connect as a new user to my "for-klaus" client, is there a way
to join an existing Process-Instance (an already launched one)?
For me, it seems that only the one (the terminal which launches the
process-definition) will see the participant-implementation-execution.
Greetings
Brain
--
you received this message because you are subscribed to the "ruote users" group.
to post : send email to [email protected]
to unsubscribe : send email to [email protected]
more options : http://groups.google.com/group/openwferu-users?hl=en
