Performance (killer?)

[Zmudzin,Tomasz,VEVEY,GL-DS/DM]

Robert,
 
there are other, more elegant ways of handling this:
 
1. You can use a so-called Check-Function Module in the event coupling. This
function module is started BEFORE the workflow gets instantiated. If it
raises an exception, no workflow is triggered. Within this FM you can also
read the event parameters and you can do any processing you wish, so it's
quite powerful.
2. If you're on 4.6c and your decision is based on a field reachable from
the event container, you can use the "Workflow start conditions" which are a
simplified version of 1.
 
Kind regards,
Tomasz
 
-----Original Message-----
From: Verlaat, Robert [mailto:Robert.Verlaat at PWN.NL]
Sent: Tuesday,20. August 2002 14:36
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Performance (killer?)
 
 
Hello,
 
 
 
I'am interested in what the system load would be when I trigger 1 Workflow
about 500 times a day, using a condition as the first step, the workflow
will "really" start about 10 times a day.
 
Would this be a performance killer for the system and should I define a new
Starting event (or use ABAP)? Or isn't it such a big problem because only 1
check has to be made? (check: if field x = 99999 end WF, else continue WF)
 
 
 
Thanks,
 
 
 
Robert
 
 
 
____________________________________________________________________________
_________________
This outbound message from KPN has been checked for all known viruses by KPN
IV-Scan, powered by MessageLabs.
 
Bezoek de Website van PWN: http://www.pwn.nl/
____________________________________________________________________________
_________________