Bookshelf Home | Contents | Index | Search | PDF | ![]() ![]() ![]() ![]() |
Siebel Business Process Designer Administration Guide for Financial Services > Designing Workflow Processes > Working with Exceptions >
Defining an Exception
Exceptions are defined in the same view as Start and Decision steps.
To define an exception
- Make the appropriate process active by selecting it in the All Processes view.
- Drag and drop an exception connector from the palette area and connect it to an existing shape on the workspace. Be sure that the end of the connector is attached to the step.
- Double-click the exception arrow in the workflow diagram.
- In the Next Step applet, select the exception and enter a name for the exception.
- Under Type, select Error Exception or User Defined Exception.
- See Defining Exception Conditions and Values to define the conditions that apply to the exception.
Defining Exception Conditions and Values
Conditions and values define the nature of the exception. In general, you define conditions that compare to the process properties' Error Code and Error Message when defining a system exception. Whenever the system encounters an error, the error code and error message are automatically populated in the process properties. To branch on a specific error, create a condition comparing to a process property, then select Error Code or Error Message and enter the code in the Values applet.
NOTE: It is recommended that you use Error Messages in your conditions rather than error codes to determine the next step in a Workflow Process. Error codes can be text-based or number-based. Because error-code numbers change from release to release, use of Error Messages is preferred.
To define exception conditions and values
- With the exception selected in the Next Step applet and the Compare applet active, choose Edit > Add New Record.
- Select a Compare To value from the picklist. The available choices are:
- Process Property. Select this when you want to compare a value in a process property with a specified value in the process instance.
- Expression. Select this when you want to use an expression, such as greater than or between, to evaluate a specific value.
- Business Component. Select this when you want to use the value in a business component field for the condition comparison.
- Applet. Select this when you want to use the value in an applet field for the condition comparison.
- Select the operation to use for evaluating the values. The available choices are:
- 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.
- 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.
- If you are using a process property value, select the name of the property from the picklist.
- If you are using a business component field, select the name of the component and the name of the field from the Business Component Name and the Business Component Field picklists.
- Enter an applet name and applet field, if applicable.
- Enter any appropriate values in the Values applet.
Bookshelf Home | Contents | Index | Search | PDF | ![]() ![]() ![]() ![]() |
Siebel Business Process Designer Administration Guide for Financial Services Published: 22 May 2003 |