WF Step Branch (H)

A WF step branch connects two workflow steps. It controls the data and process flow of a workflow process.

This object type occurs in the following location in the object hierarchy:

• Siebel Objects > Workflow Process > WF Step > WF Step Branch

The following table describes properties that Siebel CRM uses with a WF step branch.

Property	Description
Event (O) (R)	Specifies the event that this WF step branch supports. The set of events is different for different object types. If the Event Object Type property is not empty, then the Event property is required.
Event Cancel Flag (O)	Specifies how Siebel CRM handles a cancel runtime event after the workflow process finishes. This property applies only to an event that Siebel CRM can cancel. It is similar to the CancelOperation in a script. If the Event Cancel Flag property is FALSE, then Siebel CRM creates the following error when the workflow process runs: The specialized method method_name is not supported on this business component.
Event Object (O) (R)	Specifies the event that Siebel CRM applies to this WF step branch. The values that you can set in the Event Object property depends on the value that you choose in the Event Object Type property. For example, if you set the Event Object Type to BusComp, then you choose only a business component in the Event Object property, such as Account.
Event Object Type (O)	Specifies the type of object that this WF step branch references, such as business component. If the Event Object Type property is not empty, then the Event Object property is required.
Event Visibility	Specifies to use a run-time event that Siebel CRM creates in the current local session or in another enterprise session. It uses this event to resume a workflow process instance that is waiting. If the workflow process is: Persistent. You can set the Event Visibility property to Enterprise or Local. In most situations if a workflow process must wait for an event, then it must be persistent and you use Enterprise. Not persistent. If it is not required that the workflow process be persistent, then it is recommended that you set the Event Visibility property to Local. If Event Visibility is Enterprise, then a run-time event searches for a matching workflow process instance. This configuration can affect performance.
Name	Specifies the name of this WF step branch. To import or export the workflow process, the name must be unique. If it is not unique, then you cannot commit the record.
Subevent (O)	Specifies the name of the method or field in a business component that Siebel CRM monitors. You set the Subevent property only if the Object Type property is BusComp or Applet and the event is InvokeMethod or SetFieldValue. For InvokeMethod, you specify the name of the method that Siebel CRM calls. For SetFieldValue, you specify the name of the field that Siebel CRM sets.
Type	Specifies the type of WF step branch. You can use one of the following values: Condition. Use a condition for this task branch. Default. If no other conditions are met, then use this task branch. Siebel CRM ignores any conditions that are defined for this task branch. Connector. Do not use any condition branching. Error Exception. Use exception handling. This connector type captures system errors. For example, the Assignment Manager server component is not available. User Defined Exception. Use exception handling. This connector type captures errors that you define. For example, the user attempts to save an incomplete order.
User Event Name	Specifies a name that describes the user event. You must define a name that is unique and that is sufficiently long so that it remains unique for the Siebel enterprise. For example: Order Placed-Begin Processing Event for Service Request Automation-Version 2
User Event Storage	Specifies the process property that Siebel CRM uses as the destination for the payload on the incoming user event. This value can be a process property. The correlator must mark this process property.
User Event Timeout (Days)	Specifies the number days that a workflow process waits for a user event to resume operation. If the user event resides on a wait step, then you use this property. Do not set this property on a wait step.