Terminating Event

[MacPherson, Graeme (AU - Melbourne)]

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/20000929/77660553/attachment.htm