Runtime Events are quite useful feature provided in Siebel. You can minimize the level of scripting if you know how to use these runtime events effectively.
For a particular event you can invoke a WF and hence perform a set of operation. Like for eg, if you want to do certain set of operation on change of a field value, you can define a runtime event which can be given in a Start, Wait or User Interact step. These runtime events are created automatically when you activate such WFs.
I will list out some of the common issues which we encounter w.r.t. runtime events :
1) Ideally when you activate a runtime driven WF, related runtime events get created/updated(in case its already present) under Administration – Runtime Events screen > Events view with the corresponding Action Set. This being done, make sure that you manually do Reload Runtime Events from the menu 2-3 times to refresh the event cache.
2) Make sure the BO of the Workflow and BC for the Field on which you want to create a Runtime Event are same.
3) Make sure the mode of the Runtime Driven WF is Interactive Flow.
4) There could be a possibility that for a particular runtime event, there are multiple action sets. So in case there is a multiple action sets, they will get executed in order of increasing sequence and if the sequence is not defined, the action set which is created first will execute first.
5) In case you want to access these Runtime driven Workflow in a mobile client, make sure that the property value Replication is set as All under activated WF list.
6) Make sure that you have given correct values for 'Event Object Type' and 'Event Object' when you are defining a runtime event in a workflow.
7) Make sure the Workflow Process Manager component is up and running.
In case you want more details about debugging Runtime Event driven Workflows, there is a very elaborate and useful document on Oracle Support web with [id] = 473851.1
Hope the above information will save your debugging hours, Happy Exploring !!!
No comments:
Post a Comment