How do CREATED terminating events link to task?

[vijay srikanth]

Hi,

By 'Bible' you're referring to the Practical Workflow for SAP book?


Regards,
Vijay


>From: "Dart, Jocelyn" <jocelyn.dart at sap.com>
>Reply-To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
>To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
>Subject: RE: How do CREATED terminating events link to task?
>Date: Wed, 30 Nov 2005 18:55:55 +0800
>
>Hi Mike,
>
>Yes very special... CREATED events are usually raised using the special
>function module SWE_EVENT_CREATE_for_upd_task where it picks up the Work
>item Id currently in process so that it only closes the current work
>item on completion.  There's a bit on it in "the bible" and also in SAP
>Help.
>
>
>Regards,
>Jocelyn Dart
>Senior Consultant
>SAP Australia Pty Ltd.
>Level 1/168 Walker St.
>North Sydney
>NSW, 2060
>Australia
>T   +61 412 390 267
>M   + 61 412 390 267
>E   jocelyn.dart at sap.com
>http://www.sap.com
>
>The information contained in or attached to this electronic transmission
>is confidential and may be legally privileged. It is intended only for
>the person or entity to which it is addressed. If you are not the
>intended recipient, you are hereby notified that any distribution,
>copying, review, retransmission, dissemination or other use of this
>electronic transmission or the information contained in it is strictly
>prohibited. If you have received this electronic transmission in error,
>please immediately contact the sender to arrange for the return of the
>original documents.
>Electronic transmission cannot be guaranteed to be secure and
>accordingly, the sender does not accept liability for any such data
>corruption, interception, unauthorized amendment, viruses, delays or the
>consequences thereof.
>Any views expressed in this electronic transmission are those of the
>individual sender, except where the message states otherwise and the
>sender is authorized to state them to be the views of SAP AG or any of
>its subsidiaries. SAP AG, its subsidiaries, and their directors,
>officers and employees make no representation nor accept any liability
>for the accuracy or completeness of the views or information contained
>herein. Please be aware that the furnishing of any pricing information/
>business proposal herein is indicative only, is subject to change and
>shall not be construed as an offer or as constituting a binding
>agreement on the part of SAP AG or any of its subsidiaries to enter into
>any relationship, unless otherwise expressly stated.
>
>
>-----Original Message-----
>From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
>Of Mike Pokraka
>Sent: Wednesday, 30 November 2005 7:19 PM
>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
>
>_______________________________________________
>SAP-WUG mailing list
>SAP-WUG at mit.edu
>http://mailman.mit.edu/mailman/listinfo/sap-wug