How do CREATED terminating events link to task?

[Mike Pokraka]

Yep, created the methods myself (zCreateAsync), and it still behaves different
to a wait-for-change type of terminating event. I suspect that it's to do with
it being an instance-independent method, but still.... how? If the event is
raised in an update task as most CREATE's are, then it's outside the user
context, so where's the link to the task that originated the event?

The whole point behind the question is coming up with a bulletproof way to
ensure a document is created. With synch methods, it is sometimes (???)
possible to back out or cancel and the task completes. Asynch does the job,
just having a little trouble trusting something that seems to work but doesn't
make sense :-)

(African or European?) 


--- Lyal Schumann <lschumann at randwater.co.za> wrote:

> Hmmmmm. That is an interesting question, Mike. I'm too lazy to go
> searching for an asynch creation task. Is there anything in the binding
> for the terminating event on the task that might give a clue? And is the
> create method definitely instance independent?
> 
> (and what is the average air speed velocity of an unladen swallow?)
> 
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of Mike Pokraka
> Sent: 30 November 2005 10:19 AM
> To: SAP Workflow User Group
> Subject: How do CREATED terminating events link to task?
> 
> 
> Hi all, 
> 
> I'm curious as to how terminating events link to async tasks, and in
> particular what makes CREATED events 'special': 
> 
> If I my terminating event is DOCUMENT.FUBAR, anyone can fubar the
> document outside of workflow and it will complete the task. This is a
> good thing.
> 
> So the logical conclusion is that an async CREATE method with a CREATED
> terminating event will terminate itself when *anyone* creates a document
> of that type. Not so, if I use CREATED, *only* a document created by
> executing that task will terminate the task. This is a good thing, but
> how is this accomplished? I mean, even if I excecute the WI which takes
> me to a transaction and I do a '/nwhatever' to restart the same
> transaction in the same session and then create a document, the CREATED
> event gets raised but won't terminate my task. How? Why?
> 
> Any insight appreciated, 
> Cheers
> Mike
> 
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
> Disclaimer
> 
> This email and any accompanying attachments may contain confidential and
> proprietary information. This information is private and protected by law
> and, accordingly, if you are not the intended recipient, you are requested to
> delete this entire communication immediately and are notified that any
> disclosure, copying or distribution of or taking any action based on this
> information is prohibited. 
> Emails cannot be guaranteed to be secure or free of errors or viruses. The
> sender does not accept any liability or responsibility for any interception,
> corruption, destruction, loss, late arrival or incompleteness of or tampering
> or interference with any of the information contained in this email or for
> its incorrect delivery or non-delivery for whatsoever reason or for its
> effect on any electronic device of the recipient.
> If verification of this email or any attachment is required, please request a
> hard-copy version.
> 
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>