Siebel Business Process Designer Administration Guide > For Developers: Workflow Process Steps > About Start Steps >
Defining Conditions and Values for Branches, Decision Steps, and User Interact Steps
Conditions and values affect the flow of your process execution. For example, you can define a condition based on the value of a priority field. If the priority is "high," the process follows a branch that sends an email to a vice president. If the priority is "medium," the email is sent to an engineer.
You define conditions and values for branches, decision steps, and user interact steps.
To define conditions and values
- Right-click the appropriate branch in the Process Designer palette workspace and choose Edit Conditions.
The Compose Condition Criteria dialog box appears.
NOTE: The values you find listed in the Compose Condition Criteria dialog box are constrained by the business object for your workflow process, which is specified at the process level. For more information, see Using Process Designer in Siebel Tools and Field Descriptions: Workflow Processes Applet.
- In the Compare To picklist, choose a Compare To value:
- Process Property. Compares a process instance's process property value to a specified value.
- Expression. Uses an expression to evaluate a specific value.
- Business Component. Uses the value in a business component field for the condition comparison or when you are defining an expression.
- Applet. Uses the value in an applet field for the condition comparison.
- Choose the operation to use for evaluating the values:
- This Must Match. The current value must match exactly, including case.
- One Must Match. One or more values must match exactly, including case.
- All Must Match. All of the values must match exactly, including case.
NOTE: The All Must Match operation is only applicable in a scenario where a workflow branch must make a decision based on a field of a child business component. The name of the child business component is specified by the Business Component Name field of the branch. The child business component is different from the primary business component of the workflow process. It is possible for the child business component to contain multiple records. If the workflow branch uses the All Must Match comparison criterion, the branch will pass only when the field values of all child business component records match branch criteria value(s) of the branch.
- None Can Match. None of the values can match exactly, including case.
- This Must Match (ignore case). The current value must match without regard to case.
- One Must Match (ignore case). One or more values must match without regard to case.
- All Must Match (ignore case). All of the values must match without regard to case.
- None Can Match (ignore case). None of the values can match without regard to case.
- Greater Than. Value must be greater than the comparison value.
- Less Than. Value must be less than the comparison value.
- Between. Value must be between a range of values.
- Not Between. Value cannot be between a range of values.
- Is Null. Value must be null.
- Is Not Null. Value cannot be null.
- Enter an object name and field, if applicable.
- Enter any appropriate values in the Values form.
You can enter multiple records in the Values form. Workflow Processes assumes an OR condition between values.
If you selected Expression in the Compare To field, enter your expression in the Values form. The syntax is the same as the syntax used in Siebel Tools. For more information about expressions, see Siebel Developer's Reference.
NOTE: You can define multiple conditions for each branch. Workflow Processes treats multiple conditions with the AND operator. To define multiple OR conditions, use expressions.
The following example shows an expression comparing a business component field with today's date, using the OR operator, which allows you to compare multiple conditions.
([Close Date] <= Today()) OR ([Name] = 'Opportunity test1')