Identifying an Automation Solution

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

After you determine business process requirements and the actions that must be performed to meet those requirements, you can identify an automation solution.

To identify an automation solution

1. Identify the solution that most closely meets the business process requirements. The following table describes the advantages and limitations of the following automation solutions: Workflow Process, Workflow Policy, and Siebel Script.

   Solution	Advantages	Limitations
   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

2. Determine if a Workflow Process or a Workflow Policy can meet the requirement(s). The following table describes when to use a Workflow Process or Workflow Policy solution for certain key requirements. For more information about Workflow Policy, see Defining Custom Workflow Policies.

   Requirement	Possible Solution
   Capture business layer logic.	Use a Workflow Process. Workflow Process Manager and runtime 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.	Use a Workflow Process or a Workflow Policy. A Workflow Process is recommended for repetition, timeliness, and for cross functional routing through a business process.
   Perform escalations and notifications.	Use a Workflow Process or a Workflow Policy. A Workflow Process is recommended for repetition, timeliness, and for cross functional routing through a business process.
   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.
   Do bulk data uploads (where Siebel Enterprise Integration Manager is required).	Use a Workflow Policy. Workflow Policy Manager is recommended if bulk data upload occurs through Siebel EIM.