|Bookshelf Home | Contents | Index | Search | PDF|
Siebel Business Process Designer Administration Guide for Financial Services > Designing Workflow Processes > Working with a User Interact Step >
Defining a User Interact Step
To define a user interact step
- Select the appropriate process in the All Processes view.
- Navigate to the Process Designer view and double-click the User Interact icon to access the User Interact view.
NOTE: To add a user interact step to the workspace, drag and drop the User Interact icon from the palette to the workspace.
- Enter or modify the step name.
- From the picklist, select the view name to which you would like to navigate the user. Only views associated with the business object will be available in the picklist.
- Enter a description of the purpose of the user interact step.
NOTE: The user interact step is only supported if the process is invoked through a script or runtime event and the process is run locally in the application object manager.
Defining User Interact Next Step Branches
User interact steps can have multiple next step branches. Use the following procedure to define each branch.
NOTE: In this release, Workflow processes do not support parallel processing. Make sure that you define your conditions so that only one branch is valid. If an object matches the conditions in multiple branches, it will try to take all branches one at a time in a random order until the first End step is reached.
To define a next step branch
- From the Process Designer view, drag and drop the appropriate step icon for the next step in the process.
NOTE: If you have already designed the entire workflow process, including connector arrows, double-click the connector arrow attached to the user interact step, then proceed to step 4.
- Drag and drop a connector arrow to the workspace, connecting the user interact step with the new next step.
- Double-click the connector arrow to access the User Interact view and activate the Next Step applet.
- Enter or modify the branch name.
NOTE: The name of the branch must be unique or you will not be able to import or export the workflow process.
- Choose a branch type. Type values are described in Table 27.
CAUTION: You should always define a Default branch step in case some work items do not meet any of the conditions you define.
- Enter the name of the next step.
- Enter comments, if applicable.
- Go to the next procedure, Defining Conditions and Values for Next Step Branches, to define the conditions that apply to each branch.
Defining Conditions and Values for User Interact Next Step Branches
Conditions and values affect the flow of your process execution. Different actions may occur depending on which path is followed. For example, you can define a condition based on the value of a priority field, so that if the priority is equal to High, the process execution follows a branch leading to an action that sends an email to a vice president. However, if the priority is equal to Medium, the email is sent to an engineer.
To define conditions and values
- Select the appropriate branch in the Next Step applet in the User Interact view.
- Click the Conditions applet to make it active.
- 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 in the process instance with a specified value.
- Expression. Select this when you want to use an expression to evaluate a specific value. You must also select a business component if your condition is based on an expression.
- Business Component. Select this when you want to use the value in a business component field for the condition comparison or when you are defining an expression.
- Applet. Select this when you want to use the value in an applet field for the condition comparison.
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 or an expression, select the name of the component and the name of the field from the Business Component Name and the Business Component Field picklists. Select the operation to use for evaluating the values. The available choices are:
- 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 applet name and applet field, if applicable.
The applet works similar to a business component, except that it has translatable names and picklists. Only list applets can be used in conditions.
Enter any appropriate values in the Values applet.
You can enter multiple records in the values applet. Workflow Processes assumes an "or" condition between values.
If you selected Expression in the Compare To field, enter your expression in the Values applet. The syntax is the same as the syntax used in Siebel Tools. See Siebel Tools Reference for more information.
NOTE: Multiple conditions can be defined for each branch. Workflow Processes treats multiple conditions with an "and." Use expressions to define multiple "or" conditions.
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')
|Bookshelf Home | Contents | Index | Search | PDF|
Siebel Business Process Designer Administration Guide for Financial Services
Published: 22 May 2003