Siebel Business Rules Administration Guide > Integrating Rules with Siebel Runtime Events > Scenario for Using Rules to Validate Data at Runtime >

Testing Rules Modules in the Siebel Application


You can test the runtime events in the Siebel application to confirm their results.

To test the runtime events

  1. Log into the Siebel application in the same runtime environment to which you deployed the rule module.

    NOTE:  If the application is open, first log out, then log in again.

  2. Navigate to the Service Requests List view in the Service Requests screen.
  3. Create new service request records or edit existing records. Create and associate activity and activity plan records with service requests to meet the criteria of the various rules written against the Service Request business component, then check to verify that:
    • Appropriate messages display.
    • If you try to save the record with disallowed data, the correct message displays and the record is not saved until all criteria for validation are met.
    • Fields are auto-populated as designed.
  4. While in the Service Requests List view, click on a service request number to drill down into the service request.
  5. In the resulting view, click on the Activities tab.
  6. In the resulting Activities applet, create a new activity or edit an existing activity. Set its status to Unscheduled and save the record.

    Confirm that the status changes to Alerted after saving.

  7. Test the runtime event similarly in the Acitivities List view of the Activities screen. Test activities with and without an entry in the SR # field.
Siebel Business Rules Administration Guide Copyright © 2007, Oracle. All rights reserved.