Bookshelf v8.0: Best Practices for Integrating Rules with Siebel Runtime Events

Table 7 provides best practices to follow when you integrate rules with runtime events.

Table 7. Best Practices for Integrating Rules with Siebel Runtime Events
Guideline	Explanation
To optimize performance: When invoking rules on runtime events, write rules for pre events, such as PreWriteRecord, instead of the corresponding post events. This guideline is especially true when the rule invokes actions, such as set field value.	Writing for pre events improves both database server performance and application server performance.
To optimize performance: Minimize the number of invocations of the Business Rule Service business service.	Every rule module invocation incurs a CPU cost.
To optimize performance: It is preferable to implement a large number of rule statements by: Invoking the Business Rule Service business service a lesser number of times with rule modules that contain a greater number of rules, instead of Invoking the Business Rule Service business service a greater number of times with rule modules that contain a lesser number of rules	In general, invocations of the Business Rule Service business service provide a much greater impact to performance than large rule modules.