Should I model a latest end for an asynchronous task?

[Dart, Jocelyn]

Hi Fred,
That should work fine.
 
Hadn't thought of using deadlines for that particular purpose but I like it as a concept. Sounds neat.
 
I guess the only thing is how much error handling you really want to
build into your workflow.
 
I assume you are just talking about dialog steps, as of course long running
background tasks are reported by the error monitoring program as standard.
 
Regards,
        Jocelyn Dart
Consultant (SRM, EBP, Workflow)
and co-author of the book
"Practical Workflow for SAP"
SAP Australia
email: jocelyn.dart at sap.com
phone: +61 412 390 267
fax:   +61 2 9935 4880
 
 
 
 
-----Original Message-----
From: Fred Lunaspa [mailto:fredlunaspa at hotmail.com]
Sent: Monday, 31 March 2003 8:20 PM
To: SAP-WUG at mitvma.mit.edu
Subject: Should I model a latest end for an asynchronous task?
 
 
Hello,
 
Can someone tell me if it's good practice to model a latest end for a
asynchronous task in order to handle terminating events that are not raised
within a specific timeframe? Or should I not model this explicitly in my
workflow?
 
Regards,
 
Fred Kouw
 
 
 
 
_________________________________________________________________
Chatten met je online vrienden via MSN Messenger. http://messenger.msn.nl/