Terminating Event

[MacPherson, Graeme (AU - Melbourne)]

Hi Brad
 
What version are you on? I made an incorrect assumption here.
 
This excerpt is from the SAP Help version 4.6:
 
*       Single-step tasks that refer to an asynchronous object method must
always be defined with at least one terminating event. At runtime, the
relevant work item is only terminated if one of the defined terminating
events occurs.
*       Single-step tasks that refer to a synchronous object method can also
be defined with terminating events. At runtime, the relevant work item is
generally terminated when the synchronous method has been successfully
executed. But the work item is also terminated if one of the defined
terminating events occurs.
 
So, to answer your question, if the terminating event is required to give an
alternate outcome to the execution of the task (to cater for a specific
scenario) then you need to model for it and ensure that the custom event is
raised. Otherwise, if the execution of the task only has one outcome then
you dont have to worry about the terminating event.
 
 
Graeme
Deloitte Consulting, Melbourne
 
*        -----Original Message-----
From: Schroeter, Brad [mailto:BSchroeter at ti.com]
Sent: Saturday, 30 September 2000 0:53
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Terminating Event
 
 
 
Graeme,
I guess I'm a little bit confused regarding this whole thing.
 
The method is synchronous (it's actually a custom method copied from a SAP
method which was also synchronous) and it has a terminating event.  When I
look at the object type this event is a custom event.  I never could find
where this event was being raised so my plan was to to create the event when
a change document was created.  Do I even need to worry about this change
document event or the terminating event since the method is synchronous?
 
Thanks,
Brad
 
-----Original Message-----
From: MacPherson, Graeme (AU - Melbourne) [mailto:gmacpherson at dc.com]
Sent: Thursday, September 28, 2000 9:05 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Terminating Event
 
 
Hi Brad
 
This only applies to the single step task. Your single step task obviously
executes an asynchronous object method. Since asynchronous object methods
dont (and technically cant) send a return code back to the caller (like
synchronous methods), the only way the workflow knows the outcome of the
task being executed is by an event which gets raised. Once the terminating
event is raised the workflow runtime sytem knows from the way you have
modelled your workflow which path to continue down after the task has been
executed. Typically, asynchronous methods deal with update tasks and
executing a task in the workflow which is designed to perform an update does
not guarantee that the update will be successful. Therefore, the workflow
waits for confirmation (by means of the terminating event) that the outcome
has occured successfully before continuing.
 
Cheers
 
Graeme
Deloitte Consulting, Melbourne
 
 
-----Original Message-----
From: Schroeter, Brad [mailto:BSchroeter at ti.com]
Sent: Friday, 29 September 2000 6:21
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Terminating Event
 
 
 
I have a workflow task (task type WF, multi-step) which has an activity step
which calls a custom task (task type T).  This custom task uses an object
method with dialog.  This custom task has a custom terminating event.  Does
this terminating event have any effect on the workflow or does it only apply
to the single-step task level?
 
-Brad
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20001002/4538f67d/attachment.htm