Configurations That Start a Workflow Process

The following table describes the configurations (Workflow Policy, Event, and Script) that start a Workflow Process, including the limitations for each configuration.

Configuration Description Limitations

Workflow Policy

Use a Workflow Policy if Siebel CRM must detect and react to data changes that occur outside of the Object Manager. For example, changes that occur in Siebel Remote or Siebel EIM.

A Workflow Policy includes the following limitations:

  • Making changes requires database downtime

  • Relatively complex to define

Event

Use an event in the following situations:

  • You must configure a basic entry point for a Workflow Process or a simple custom action.

An event includes the following limitations:

  • You cannot write script on the object event to reply directly to an event.

  • Can be more difficult to send the event context to business logic.

  • Only detects data changes that the Object Manager component makes.

Script

Use a script in the following situation:

  • You want to perform some complex processing before deciding to invoke the Workflow Process.

Invoking a Workflow Process from a script includes the following limitation:

  • Because a script in written in the Application Object Manager, it cannot respond directly to database layer events, such as Siebel Remote or EIM changing a record at the database level.