Workflow Process

This solution includes the following advantages:

• Visual representation of business logic is simple to understand and maintain
• Remote synchronous and asynchronous capability provides compatibility across Siebel CRM for scalability and long-running transactions

This solution includes the following limitations:

• The semantics for control are not as rich as with scripting
• Limited control of flow for iteration through record sets
• Limited direct access to object methods

Workflow Policy

This solution includes the following advantages:

• Replies to a database event regardless of whether or not an Object Manager server component starts the policy
• Can realize higher transaction throughput for a simple transaction

This solution includes the following limitations:

• Policy changes might require database downtime
• More difficult to define than other alternatives
• Provides only a limited range of actions

Siebel Script

This solution includes the following advantages:

• Familiar to many developers
• Provides a set of semantics
• Is flexible

This solution includes the following limitations:

• More difficult to maintain and upgrade
• Slower performance

Capture business layer logic.

Use a workflow process. Workflow Process Manager and run-time events capture business layer logic.

Use features that a workflow process supports but that workflow policy does not support.

Use a workflow process. A workflow process can provide pause, stop, and error handling capabilities.

Implement complex comparison logic or flow management.

Use a workflow process. A workflow process is recommended to develop and deploy, and to perform complex comparison logic and flow management. For example, through IF, THEN, ELSE, or CASE.

Call a business service.

Use a workflow process. A workflow process can call a business service.

Use a repeating component request.

Use a workflow process. You can set up a workflow process from a repeating server component request but not from a workflow policy.

Repetitive, manual processing.

Use a workflow process. A workflow process is recommended for repetition, timeliness, and for cross functional routing through a business process.

Process an event in a timely fashion.

Perform escalations and notifications.

Capture data layer logic.

Use a workflow policy. Workflow Policy Manager captures data layer logic. Data coming into Siebel CRM in the data layer is not captured in the business layer. This requirement typically indicates a potential candidate for a workflow policy. Example data coming into Siebel CRM in the data layer includes data coming through EIM or MQ channels.

Use features that a workflow policy supports but that a workflow process does not support.

Use a workflow policy. A workflow policy can support some features that are not available or that are difficult to support with a workflow process. For example, email consolidation, duration, and quantity.

Do bulk data uploads.

Use a workflow policy. Workflow Policy Manager is recommended if bulk data upload occurs through EIM.

Do data quality cleaning in the data layer.

Use a workflow policy. Workflow Policy Manager is recommended for working in the data layer.