Bookshelf Home | Contents | Index | PDF |
Siebel Business Process Framework: Workflow Guide > Manipulating Data in a Workflow Process > Configuring a Decision Condition for a Workflow Process > Configuring a Decision ConditionTo define conditional logic in a workflow process, you define conditions and values that determine the path that the workflow process pursues. For example, you can define a decision condition that uses the value of a priority field:
You can define a decision condition for the following items: Viewing an Example of a Decision ConditionThis book includes several examples that use a decision condition. Here are two examples:
Adding a Branch ConnectorA branch connector is a type of connector in a workflow process that can include a decision condition. You define conditional logic on a connector that emanates out of the step, and not on the step itself. A branch connector typically emanates from a start step, decision point, wait step, or user interact step.
Creating a Decision Condition on a Branch ConnectorYou can use the Compose Condition Criteria dialog box to define a decision condition on a branch connector. A branch connector can be a connector that emanates from a start step, decision point, wait step, or user interact step. The Compose Condition Criteria dialog box constrains the values that it lists according to the Business Object property of the workflow process. For an example that uses conditional logic on a connector, see Defining a Decision Condition for the Decision Point. To create a decision condition on a branch connector
Adding Multiple Branches to a Single Workflow Process StepA start step, decision point, wait step, or user interact step can each reference multiple branch connectors. CAUTION: If you define multiple branch connectors, then make sure you define at least one connector with the Type property set to Default. This configuration makes sure an exit route exists if a work item does not meet any of the decision conditions. If you do not do this, then you might create an infinite loop. To add multiple branches to a single workflow process step
Comparison of Branching Declaratively to Programming with a ScriptYou can implement branching declaratively, as in multiple branches that emanate from a single workflow process step. In some situations, you can achieve the same result through a script, as in scripting on a business service. For example, assume a STATUS field references a List of Values (LOV), and this LOV includes 120 values. If the user updates the STATUS field, then a workflow process performs 100 different updates in three different business components. This workflow process contains a start step that examines 120 decision conditions, and then uses 100 different branches. Each branch updates a business component. As an alternative, you can create a workflow process that includes a scripted business service. This workflow process sends the STATUS to the business service. The business service computes, and then propagates the outcome to the business components through the same business service or through a separate Siebel operation step in the workflow process.
Using Parallel Processing in a Workflow ProcessSiebel Workflow does not support parallel processing. Make sure you define decision conditions so that the workflow process can only proceed along one connector. If you do not do this, then Oracle cannot predict the run-time behavior of the Workflow Engine. |
Siebel Business Process Framework: Workflow Guide | Copyright © 2018, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |