Siebel Business Rules Administration Guide > Implementing Rules in Scripts >

Best Practices for Implementing Rules in Scripts


Table 8 provides best practices to follow when you implement rules in scripts.

Table 8. Best Practices for Implementing Rules in Scripts
Guideline
Explanation

Independent of how you call the Business Rule Service business service, to capture its output data, you must provide custom script that calls the Business Rule Service business service and parses its output property set.

 

To optimize performance:

When directly invoking the Business Rule Service business service, such as from scripts or workflow, it is recommended to set the GetMoreData input property to N if you can construct the necessary data required for the BusCompList input property.

 

For a given business component that has been imported into HaleyAuthority, various descendant business components and fields may have been imported into HaleyAuthority. For a given rules module that acts on the business component, it is likely that only a subset of the business component's descendant business components and fields are used by the rule module.

Setting GetMoreData to N requires you to explicitly provide the business component-field hierarchy to the BusCompList input property, but it avoids having to process the entire hierarchy of a business component when the rule module executes.

To optimize performance:

Minimize the number of invocations to 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.

 

Siebel Business Rules Administration Guide Copyright © 2007, Oracle. All rights reserved.