Advise about use of events

[Breslavets, Sergey]

Hi Robert,
 
since the workflow starting conditions are checked after the event creation,
it's logged in the system. It shows you that the event was triggered and the
receiver could not be started because the start conditions were not met.
This is not bad and, on contrary, it can be useful to you to analyze your
processes.
 
The only drawback of this is that the event is still being raised, which
consumes certain system resources (work processes). If it gets triggered with
significantly higher frequency then receivers are started you might want to
consider checking conditions before the event is raised - can make your system a
little more efficient... e.g. if you trigger event on each PO change but start
receivers only when certain fields are changed, you can evaluate which field is
changed before triggering the event to not even raise it if conditions are not
met. (Here I'm assuming that the event does not trigger other receivers with
different start conditions).
 
Thanks,
Sergey
 
 
 
-----Original Message-----
From: Robert vdBerg [mailto:Robert.vande.Berg at nuon.com]
Sent: Friday, June 06, 2003 6:26 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Advise about use of events
 
 
Hello fellow workflow developers,
 
I have developed several workflows which are triggered with the same event.
I have created start conditions which look at a parameter of the event. This
works fine, but I still have a question.
 
When I trigger the event, the eventtrace has some error events. These are
the events with the startcondition that doesn't match with the value of the
event parameter.
 
Is this bad and should I replace the startcondition with a receiver function
module?
 
Thanks in advance!
 
Robert van den Berg
Accenture Technology Solutions