|
Siebel Business Process Framework: Workflow Guide > Administering Workflow Policies > About Workflow Policy Administration >
Converting a Workflow Policy to a Workflow Process
In general, it is recommended you keep workflow policies simple, placing most business logic into a workflow process. To this end, in many cases you can convert a workflow policy to a workflow process. Table 77 describes guidelines you can follow when converting a workflow policy to a workflow process.
Table 77. Guidelines for Converting a Workflow Policy to a Workflow Process
To Replace This Configuration Used in a Workflow Policy . . . |
. . .Use This Configuration in a Workflow Process |
A specialized operator, such as IS UPDATED or IS ADDED. |
A runtime event. |
A standard operator, such as = or <>. |
A condition branch or decision step. |
A workflow policy program that performs an operation at the database layer. |
A Siebel Operation step at the object layer that implements logic which manipulates data at the data layer. Although a workflow process cannot call a workflow policy program, if there is a need to perform an operation at the database level it might be possible to use the Siebel Operation step to accomplish the same required functionality. |
(This cell left intentionally empty.) |
For sending email, since a workflow process uses the communication outbound manager service, it can use recipient group and exact email address. |
|
