Siebel Business Rules Administration Guide > Troubleshooting Siebel Business Rules >

Troubleshooting Rules Implementation


This topic provides information for resolving issues that are particular to implementing rule modules in various contexts - runtime events, Siebel workflows, Siebel Task UI flows, or script.

Table 21. Troubleshooting Rules Implementation
Context
Symptoms/Error Messages
Diagnostic Steps/Cause
Solution

Runtime event

At runtime, you get an error message that the deployed rule does not exist.

The name of the rule module in the Business Service Context field for the runtime event's Action must be identical to the name of the rule module in HaleyAuthority. The comparison is case-sensitive and space-sensitive.

Correct the rule module name in the Business Service Context field for the runtime event's Action.

For more information, see Repeat Step 4 through Step 5 for the Service Request Activity - PreWriteRecord module. In the Rule Module Relation applet, create a new record as follows:.

Runtime event

At runtime, you get an error message that the deployed rule does not exist.

 

The name of the rule module should not include any special characters, such as *, ?, /, !, @ or quotes.

  1. Deactivate the rule module.
  2. In HaleyAuthority, rename the rule module.
  3. Redeploy the module.
  4. Activate the module, which now appears as a new module.
  5. Enter the corrected module name in the Business Service Context field for the runtime event's Action.

For information on each of these steps, see Scenario for Using Rules to Validate Data at Runtime.

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