Siebel Business Process Designer Administration Guide for Financial Services > Designing Workflow Processes > Working with a User Interact Step >

Using the User Interact View


This view is for entering and viewing the details for a user interact step. A user interact step is used to represent the step in the process flow where a Siebel view is presented to the end user. The user can select an action associated with a runtime event that will then branch the process to the next appropriate step.

The tasks you can perform in this view are:

NOTE:  This release does not support backward navigation in a workflow process that involves user interact steps. Going backward in a workflow process with user interact steps causes the workflow process instance to lose context, which may result in errors with messages such as: "Cannot resume process 'PROCESS_INSTANCE_ID' for object 'OBJECT_ID'. Verify that an instance does exist and has a 'Waiting' status."

User Interact Applet Field Descriptions

Table 26 describes the fields where you enter data in the User Interact applet.

Table 26. User Interact Applet Fields
Field
Description
Possible Value
Name
The name of the user interact 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.
Business object of the parent process. The business object determines the business components that are available for conditions. This is a read-only field.
Type
The type of step.
This value is automatically entered when you create the step in the Process Designer view. This is a read-only field.
Description
A text narrative describing the purpose of the user interact step.
Free-form text.
Created By
The name of the person who creates the process.
This value is automatically entered based on the log on name of the user.
Created
The date and time that the process is created.
This value is automatically entered.

Next Step Branches Applet Field Descriptions

Table 27 describes the fields in the Next Step Branches applet.

Table 27. Next Step Branches Applet Fields
Field
Description
Possible Value
Name
The name of the next step 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 the following choices:
  • Condition. This value indicates that a condition is defined for the branch.
  • Default. This value indicates that if nothing else is satisfied, this branch will be followed. Additionally, if this value is used, any conditions defined for the branch are ignored.
  • Connector. Use this value when 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.
Picklist of existing process steps.
Comments
Additional statements relative to the decision branch.
Free-form text.
Event Object Type
The type of the object the event refers to. This is used when defining a runtime event.
Optional
  • Application.
  • Applet.
  • BusComp.
Event
The specific event the object supports.
Required if Event Object Type is specified. The set of events is different for different object types.
Event Object
The name of the object.
Required if Event Object Type is specified. This is the name as defined in Tools. The set of objects is different for different object types.
Sub Event
An options parameter for the event.
Optional
For InvokeMethod, the name of the method being invoked. For SetFieldValue, the name of the field being set.
Event Cancel Flag
Abort the runtime event after executing the process.
Optional
This flag only applies to events that are cancelable. This flag functions like CancelOperation in scripting.

Conditions Applet Field Descriptions

Table 28 describes the fields in the Conditions applet.

Table 28. 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. This displays a picklist of process properties.
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.
The picklist includes business components defined for the business object selected for the process.
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.
The picklist displays all fields defined for the selected business component.
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.
The picklist displays all fields defined for the selected applet.

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