Best Practices?

[Dart, Jocelyn]

Thanks Ravi, 
 
Exactly so! 
 
And even for the volume situations you have the event queue - which lets you smooth out the volume, and also lets you redeliver any failed events from the event browser. 
 
As for events being "tricky" because they can be raised in multiple places - that's what makes the event so useful - your workflow will be started/ended by the event regardless of what scenario you are using.  
 
And by the way if  you dislike HCM workflows so far  ... look out for the HR Admin Services solution in ECC 6.0 Enhancement Pack 2 - very very cool stuff. 
 
Starting workflows directly is an avenue of last resort in a production environment. 
 
Regards,
Jocelyn 

________________________________

From: sap-wug-bounces at mit.edu on behalf of Ravi Dixit
Sent: Fri 17/08/2007 11:14 AM
To: sap-wug at mit.edu
Subject: Re: Best Practices?


Hi Hal
 
The standard setup in SAP is generally via events. Most of the business processes trigger events which are used by most developers as the primary method of workflow trigger. This enables better monitoring through the Event trace, event queue, etc. These are not possible while kicking off workflows directly, where you may have to pass messages back to the initiating application if there were problems starting the workflow, which in most instances may not be meaningful to the end user. Also, the single great feature of event mechanism is the ability to retrigger them from SWUE by just passing the object key (in most instances).