<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.2802" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV><SPAN class=383225217-15032006><FONT face=Arial color=#0000ff size=2>I
thought that might be the case, but I just wanted to check to see if there was a
possible work around. Thank you for the input.</FONT></SPAN></DIV>
<BLOCKQUOTE>
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu]<B>On Behalf Of </B>Mark Pyc<BR><B>Sent:</B>
Wednesday, March 15, 2006 1:48 AM<BR><B>To:</B> SAP Workflow Users'
Group<BR><B>Subject:</B> Re: Dialogue step after 'wait for
event'<BR><BR></FONT></DIV>
<DIV>G'day Bill,</DIV>
<DIV> </DIV>
<DIV>Just to clarify...</DIV>
<DIV> </DIV>
<DIV>You have n foreground steps. A wait for event. Subsequent foreground step
with same agent as the step before the wait?</DIV>
<DIV> </DIV>
<DIV>If this is your chain then yes you are right the wait for event will
break the advance with dialog sequence. This is the way it is meant to be.
Because you need to wait for an ansyncronous update (presumably) to occur. The
nature of asynchronous updates is that the dialog users context is free from
having to wait for the update to occur. </DIV>
<DIV> </DIV>
<DIV>Even though it may only take a fraction of a second in practice normally,
there can be delays during which the user could navigate entirely away from
the SAP Inbox. </DIV>
<DIV> </DIV>
<DIV>SAP is a client server set-up. Once the dialog chain is broken, it can't
be re-established by the server.</DIV>
<DIV> </DIV>
<DIV>The same would be true if your previous step was declared as an async
method and your wait step was replaced by the terminating event. The chain
would still be broken.</DIV>
<DIV> </DIV>
<DIV>It's just a case of training your user to refresh their inbox and execute
the next item. Might even be worth including a reminder to do so in the long
text of the step prior to the wait.</DIV>
<DIV> </DIV>
<DIV>Good luck,</DIV>
<DIV>Mark<BR><BR> </DIV>
<DIV><SPAN class=gmail_quote>On 3/14/06, <B class=gmail_sendername>Bill
Holbrook</B> <<A href="mailto:BHolbro@smud.org">BHolbro@smud.org</A>>
wrote:</SPAN>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><BR>
Hello.<BR><BR> I am currently on SAP
release 4.7, Basis patch level
SAPKB62050.<BR> I have written a
workflow that has a 'Wait for event' step. Before the step executes there
are steps that are executed in dialog mode. When the 'Wait for event' step
is executed, it sends an item for the next step to be executed into my inbox
rather than just continuing with the rest of the workflow. The 'Wait for
event' step seems to go into background mode (WF-BATCH) and that is why the
item is going into my inbox instead of executing automatically. Is there a
way to make the workflow continue after the 'Wait for event' step
has executed and not create an inbox item ? <BR><BR>Bill
Holbrook<BR>Technical Developer<BR>Sacramento Municipal Utility
District<BR>Mail Stop A306 (916)
732-6759<BR><BR><BR><BR>_______________________________________________<BR>SAP-WUG
mailing list<BR><A href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</A><BR><A
href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</A><BR></BLOCKQUOTE></DIV><BR></BLOCKQUOTE></BODY></HTML>