Wait step triggered by event raised within current workflow i nstance

[de Valensart Schoenmaeckers, Patrick]

Peter,
 
I've had pretty much the same issue and here is the solution I found:
 
>From the wait for event step, pass the eventparameter container element
"_evt_creator" to a workflow container element. Then put the wait for event
step in a loop where you test that your workflow container element (that now
contains the username who did the change and raised the event) is not equal
to USWF-BATCH. If the result is true, the loop ends and the workflow
continues towards the fork end, otherwise, it goes by a new loop pass and
"listens" again to BUS2012 SIGNIFICANTLYCHANGED.
 
Hope this helps.
 
Patrick
 
-----Original Message-----
From: Peter Abram [mailto:peterabram at hotmail.com]
Sent: Tuesday, January 14, 2003 14:52
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Wait step triggered by event raised within current workflow
instance
 
A parallel (fork) branch of the workflow contains a wait step listening for
event BUS2012 SIGNIFICANTLYCHANGED - with the intention of terminating the
current instance if significant changes are made to the purchase order
outside of the current workflow instance.
 
The event BUS2012 SIGNIFICANTLYCHANGED event can be raised within the
current workflow instance because there is a step referencing transaction
ME22N.
 
How do I prevent the branch containing the wait step from reacting to the
execution of the ME22N work item within the current workflow instance
(assuming the agent does make a significant change)?
 
 
_________________________________________________________________
MSN 8 with e-mail virus protection service: 2 months FREE*
http://join.msn.com/?page=features/virus