|
Siebel Business Process Framework: Workflow Guide > Developing Workflow Processes > Process of Planning Workflow Processes >
Determining How to Start a Workflow Process
This task is a step in Process of Planning Workflow Processes. During the planning phase of a development effort you can determine if a run-time event, user event, workflow policy, or a script starts the workflow process. For more information, see Starting a Workflow Process. To determine how to start the workflow process
- Consider the advantages and limitations of each configuration that can start a workflow process that this topic describes, and then choose the configuration that most closely matches the business requirements.
Using a Workflow Policy to Start the Workflow Process
A workflow policy starts a workflow process after a database change. If the workflow policy conditions are met, then an action occurs. In some situations, the action calls the Workflow Process Manager server component to run a workflow process. Processing that a workflow policy starts does not occur in real time. The following are typical uses of a workflow policy:
- EIM batch processing
- Siebel EAI inserts and updates
- Manual changes from the user interface
- Assignment Manager assignments
- Siebel Remote synchronization
Using an Event to Start the Workflow Process
You can use the following events to start a workflow process:
- Run-time event. A run-time event occurs if a change occurs in the client or in the business component. Processing that a run-time event starts occurs in real time.
- User event. A user event is a unique event that is internal to Siebel Workflow. It starts or resumes a long-running workflow process. The User Event business service creates a user event.
You can define an event from the administrative interface for one of the following object types:
- Application
- Applet
- Business Component
Using a Script to Start the Workflow Process
A script can start a workflow process programmatically as a business service. The Workflow Process Manager server component includes APIs that you can use with a script to start a workflow process from an external system. The Object Manager starts a script. You can add a script to one the following object types:
- Application
- Applet
- Business Component
- Business Service
Summary of Configurations That Start the Workflow Process
Table 7 summarizes some of the configurations that can start a workflow process.
Table 7. Configurations That Start the Workflow Process
|
|
|
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.
- You must avoid distributing the Siebel Repository File (SRF). For example, because of the burden created for mobile users.
|
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 situations:
- You must write a script directly in reply to an event.
- Siebel CRM must access an applet event that only Siebel Tools displays.
|
A script includes the following limitations:
- You must distribute changes through a new Siebel Repository File (SRF).
- Only detects data changes that the Object Manager component makes.
- You must write the script on an object event.
|
| 
