Siebel Business Process Designer Administration Guide for Financial Services > Designing Workflow Processes > Working with Decision Steps >

Using the Decision Branches View


This view is for entering and viewing the details for a Decision step. A decision can contain many branches. Each branch is based on multiple conditions.

The top portion of the view, the Decision applet, is where you can perform various tasks. The lower portion has three applets: Branches, Conditions, and Values.

The tasks you can perform in this view are:

Decision Applet Field Descriptions

Table 10 describes the fields where you enter data in the Decision applet.

Table 10. Decision Applet Fields
Field
Description
Possible Value
Name
The name of the decision step.
A descriptive name that is:
  • Consistent with your overall naming strategy
  • Meaningful to the process designer
Business Object
The name of the associated business object.
Read-only.
Type
The type of the step.
This value is automatically entered when you create the step on the Process Designer view.
Description
A text narrative describing the purpose of the decision step.
Free form text.
Created By
The name of the person who creates the process.
Read-only.
This value is automatically entered based on the logon name of the user.
Created
The date that the process is created.
Read-only.
This value is automatically entered.

Branches Applet Field Descriptions

Table 11 describes the fields in the Branches applet.

Table 11. Branches Applet Fields
Field
Description
Possible Value
Name
The name of the branch.
The name of the branch must be unique or you will not be able to import or export the workflow process.
Type
The type of branch.
The value can be one of two choices:
  • Default. This value indicates that if all conditional branches fail, this branch will be followed.
  • Condition. Define zero or more conditions. If no conditions are defined, it means the branch always passes.
  • Connector. Use this value whenever there is no condition branching involved.
  • Error Exception. Use this value to define exception handling. This connector type captures system errors, such as an error noting that the Assignment Manager server component is not available. For more information, see Working with Exceptions.
  • User Defined Exception. Use this value to define exception handling. This connector type captures user-defined errors, such as an error noting that an order being submitted is incomplete. For more information, see Working with Exceptions.
Next Step
The name of the step that follows when conditions are met.
 
Comments
Additional statements relative to the branch.
 

Conditions Applet Field Descriptions

Table 12 describes the fields in the Conditions applet.

Table 12. Conditions Applet Fields
Field
Description
Possible Value
Compare To
Indicates where the comparison value is coming from.
This is a required field, with the following choices:
  • Business Component
  • Process Property
  • Expression
  • Applet
Operation
Identifies the comparison operation
  • 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.
  • 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.
Property Name
Identifies the specific business process property on which to base the condition.
This is a required field when Process Property is the Compare To value.
Business Component
Identifies the specific business component on which to base the condition.
This is a required field when Business Component or expression is the Compare To value.
Business Component Field
Identifies the specific field within the business component on which to base the condition.
This is a required field when Business Component is the Compare To value.
Operation
The type of operation to perform on the comparison value.
A picklist contains the possible values for this required field.
Applet Name
The name of the applet to compare.
This is a required field when Applet is the Compare To value.
Applet Field
The name of the field within the named applet.
This is a required field when Applet is the Compare To value.

Values Applet

The Values applet is dynamic based on the Compare To field in the Conditions applet. The Values applet is for storing data to be used in the condition evaluation.


 Siebel Business Process Designer Administration Guide for Financial Services 
 Published: 22 May 2003