Runtime Event Behavior

If a runtime event starts a Workflow Process, then Siebel CRM sends the business component instance that starts the runtime event to Siebel Workflow. The row that the Object Id property defines receives this runtime event. Siebel Workflow receives and processes this event only if the business component and the Workflow Process references the same business object. If Siebel Workflow can receive this event, then Siebel CRM sets the Object Id process property to the active row of the primary record in the business object.

If the business component that starts the runtime event is not the primary business component, then Siebel CRM does not update the active row of the business component in the Object Id process property, and it must get this row through some extra processing.

The long-running, interactive, and service Workflow Processes use the following behavior:

• The Object Id must match the Row ID of the active row for the primary business component. If the Object Id process property is different from the active row, then Siebel CRM runs the primary business component again to make the active row the same as the Object Id.

• To change the active row, you can configure Siebel CRM to assign a new Row Id to the Object Id property. If Siebel Workflow detects that a new Row Id is assigned to the Object Id property, then it runs the business component again and makes the new Row ID the active row.

• If you set the Object Id to an empty string, then Siebel Workflow does not enforce the must match rule. However, Siebel Workflow cannot use objects that require an Object Id, such as the runtime event or Siebel operation step, until it sets the Object Id to a new Row ID.