|
Business Processes and Rules: Siebel eBusiness Application Integration Volume IV > Creating and Using Dispatch Rules >
Differences Between EAI Dispatch Service and Workflow
Although the EAI Dispatch Service is very similar to Siebel Workflow in initiating a task based on a condition, there are some limitations in Siebel Workflow that you can overcome using the EAI Dispatch Service. Siebel Workflow operates on business components as opposed to property sets, so Siebel Workflow can only branch based on fields in a business component. Furthermore, with Siebel Workflow you cannot route incoming documents based on property sets since the workflow decision points cannot search inside of arbitrary property sets. Table 5 provides some guidance to help you determine the best method for your business requirements.
Table 5. Siebel EAI Dispatch Methods and Workflow
|
|
|
|
Need to route the incoming document based on its structure or content |
3 |
|
The EAI Dispatch Service can route incoming documents based on property sets, whereas workflow can only branch based on fields in a business component. |
Multiple dispatch targets |
3 |
|
The EAI Dispatch Service is a better choice because writing a workflow to include every branch can be unwieldy, but you can have many EAI Dispatch Service rules. |
Need to change input property set before dispatching |
3 |
|
The EAI Dispatch Service is the better choice since it has more powerful mapping capabilities than workflow. |
Need more complex processing on the input message before dispatching |
|
3 |
The EAI Dispatch Service can branch based on the content of the input document, whereas workflow can branch based on business service. |
Workflow options are sufficient for your requirements |
|
3 |
In this case, Siebel Workflow is the best choice. |
|
