Siebel Business Process Framework: Workflow Guide > Developing a Workflow Process > Process of Analyzing Business Requirements >

Identifying an Automation Solution


This task is a step in Process of Analyzing Business Requirements.

Once you have determined process requirements, you can identify the automation solution that meets your business requirements. Table 7 summaries the solutions available for automating processes. When making implementation decisions, it is recommended you consider the advantages and limitations of each solution.

Table 7. Comparison of Siebel Workflow to Other Siebel Automation Solutions
Framework
Advantages
Limitations

Workflow Process

Visual representation of business logic is relatively simple to understand and maintain.

Remote synchronous and asynchronous execution allows horizontal scalability and long-running transactions.

The semantics for control are not as rich as with scripting. Specific limitations include:

  • Limited control of flow for iteration through record sets.
  • Limited direct access to object methods.

Workflow Policy

Policies respond to database events regardless of whether they are initiated by an Object Manager component or by a non-Object Manager component.

Policies can get higher transaction throughput on a given set of hardware for simple transactions.

Changes to policies can require database downtime to implement.

Policies are more difficult to configure that other alternatives.

Policies allow a limited range of executable actions.

Siebel Script

Script is familiar to many developers.

Script provides a set of semantics.

Script is flexible.

Limitations for scripting include:

  • Ease of maintenance.
  • Ease of upgrade.
  • Performance.

Comparing Workflow Processes and Workflow Policies

Table 8 summarizes some common requirements and recommends a workflow process or a workflow policy solution.

Table 8. Comparison of Siebel Workflow to Other Siebel Automation Solutions
Requirement
Recommended Solution
Description

Capture business layer logic.

Workflow Process

Workflow Process Manager and run-time events capture business layer logic.

Capture data layer logic.

Workflow Policy

Workflow Policy Manager captures data layer logic.

Data coming into Siebel through the data layer, for example EIM or MQ channels, is not captured through the business layer. This requirement typically indicates a potential candidate for a workflow policy.

Implement features supported by a workflow policy but not a workflow process.

Workflow Policy

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

Implement features supported by a workflow process but not a workflow policy.

Workflow Process

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

Implement complex comparison logic, or flow management.

Workflow Process

A workflow process provides a better platform for development and deployment, complex comparison logic, and flow management, such as IF, THEN, ELSE, or CASE.

Invoke a business service.

Workflow Process

A workflow process can invoke a business service.

Perform bulk data uploads.

Workflow Policy

Workflow Policy Manager is the better alternative when bulk data uploads occur through EIM .

Perform data quality cleaning in the data layer.

Workflow Policy

Workflow Policy Manager is the most appropriate solution for working at the data layer.

Use a repeating component request.

Workflow Process

You can setup a workflow process from a repeating component request but not a workflow policy.

Repetitive, manual processing.

Workflow Process

The structure of a workflow process provides a superior solution for repetition, timeliness, and cross-functional routing through a business process.

Process an event in a timely fashion.

Workflow Process

Perform escalations and notifications.

Workflow Process

For more information, see About Workflow Policies.

Siebel Business Process Framework: Workflow Guide Copyright © 2008, Oracle. All rights reserved.