Order of Events
July 19th, 2007
A quick list, for reference:
- Runtime Applet.PreInvokeMethod
- Browser Applet_PreInvokeMethod
- Server WebApplet_PreInvokeMethod
- Runtime BusComp.PreInvokeMethod
- Server BusComp_PreInvokeMethod
- Runtime BusComp.InvokeMethod
- Server BusComp_InvokeMethod
- Runtime Applet.InvokeMethod
- Server WebApplet_InvokeMethod
- Browser Applet_InvokeMethod
Essentially, the Runtime Event occurs before the equivalent server script event for the same object, plus the Applet browser script events ‘wrap’ all server side events.All of which makes perfect logical sense, but it’s sometimes handy to see it written down in a list.
Entry Filed under: Configuration, Scripting, Siebel, Workflow
3 Comments Add your own
1. SKV | March 28th, 2008 at 5:39 am
I am little bit worried about the placement of runtime event. I found following extract from document “477992.1″ which says;
=======================
4. Problem: If a buscomp has code on WriteRecord and the runtime event fires on Writerecord, which occurs first? Solution: WriteRecord runtime event is in essence a Post-WriteRecord event and will be fired AFTER the buscomp code is executed.
=========================
so that means that first Tool WriteRecord will be fired & then run time event which is contrary to what you said.
Waiting for your reply
2. stuandgravy | March 28th, 2008 at 10:21 am
Never trust documentation, that’s my motto!
To get the list above I logged all the different events and the WriteRecord Runtime Event definitely fires before the WriteRecord Event. That’s true, at least, for Siebel 7.8. I don’t have other versions to hand to confirm.
3. Notes On Siebel » O&hellip | March 30th, 2008 at 9:39 pm
[...] commented on my Order of Events post from July pointing out a contradiction he spotted in TechNote 581. On [...]
Leave a Comment
Some HTML allowed:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
Trackback this post | Subscribe to the comments via RSS Feed