This actually rings a bell. I believe there is an OSS note to correct the situation (no idea of the number I'm sorry).<br><br>
<div><span class="gmail_quote">On 7/3/06, <b class="gmail_sendername">Mike Pokraka</b> <<a href="mailto:asap@workflowconnections.com">asap@workflowconnections.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Right you are, I see the problem. I had it the wrong way around - the<br>advance with dialog setting refers to the START of the task. Easy but
<br>annoying to work around (disable it at header and enable it for all<br>other steps), but I'd agree that it should not be disabled in the builder.<br>Sorry if that was a misleading answer, I don't have a system handy I can
<br>check with. I'm now not too sure whether this is the case with later<br>versions either.<br><br>Cheers,<br>Mike<br><br>clucking wrote:<br>> Thanks Mike for your quick reply,<br>><br>><br>><br>> I think you are right but to me it is in a way the end of the task
<br>> execution (update) which is asynchronous and not the start, and then the<br>> start could be advance with dialog? Then it would be the next step(s)<br>> where Advance with dialog would be impossible, because the first one is
<br>> ended by a terminating event and not the user.<br>><br>><br>><br>> Thanks,<br>><br>> Claus.<br>><br>><br>><br>> ------------------------------------------------------------------------
<br>><br>> *From:* <a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a> [mailto:<a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a>] *On<br>> Behalf Of *Mike Pokraka<br>> *Sent:* 3. juli 2006 10:21
<br>> *To:* 'SAP Workflow Users' Group'<br>> *Subject:* RE: Asynchronous task and Advance with Dialog.<br>><br>><br>><br>> Hello,<br>><br>> Advancing in dialog is a synchronous process. Asynchronous tasks are…
<br>> well, asynchronous, so the advance with dialog setting is completely<br>> irrelevant so my guess is it just shows the default.<br>><br>> Cheers,<br>><br>> Mike<br>><br>><br>><br>> ------------------------------------------------------------------------
<br>><br>> *From:* <a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a> [mailto:<a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a>] *On<br>> Behalf Of *clucking<br>> *Sent:* 03 July 2006 08:50
<br>> *To:* <a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a><br>> *Subject:* Asynchronous task and Advance with Dialog.<br>><br>><br>><br>> Hi all,<br>><br>><br>><br>> In a 4.6C system, I cannot deselect "Advance with Dialog" for
<br>> asynchronous tasks in the step definition. It can only be controlled by<br>> changing the common indicator on header level of the definition but then<br>> the indicator of cause is removed for all steps. Is it a bug? – or why
<br>> this behavior.<br>><br>><br>><br>> Thanks in advance,<br>><br>><br>><br>> Clucking.<br>><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><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>