Siebel Business Process Framework: Workflow Guide > Creating a Workflow Process > Creating the Workflow Process Object Definition >

Defining the Primary Business Component


The primary business component is the business component that the Primary Business Component property of the business object references. The Business Object property of the workflow process references this business object. If the Primary Business Component property of the business object does not reference the business component that starts a run-time event, then Siebel CRM does not save the active row of the business component in the Object Id process property. In this situation, you must configure Siebel CRM to get it through some extra processing.

The business object that a workflow process references must contain a primary business component.

To define the primary business component

  1. In Siebel Tools, in the Object Explorer, click Business Object.
  2. In the Business Objects list, query the Name property for the business object that your workflow process references.
  3. In the Properties window, in the Primary Business Component property, choose a business component.

Updating Fields That Reside in Nonprimary Business Component

You can configure Siebel CRM to update a field that resides in a nonprimary business component.

To update fields that reside in nonprimary business component

  • Make sure one of the following situations exists:
    • A join exists between the base table of a primary business component and the field that Siebel CRM must update.
    • A link exists between the primary business component and the business component that contains the field that Siebel CRM must update.

For example, assume Siebel CRM must update sales stage data in a workflow process, and that the Business Object property of this workflow process is set to Opportunity. The predefined Sales Stage join on the Opportunity business component allows Siebel CRM to update the Sales Stage field.

Guidelines for Configuring Joins and Links

If you configure joins or links, then it is recommended that you use the following guidelines:

  • If a predefined join or link does not exist, then you can define one.
  • In some situations, to update a field in a nonprimary business component, you can copy an existing business object, and then define it in the Business Object property of a workflow process. If you choose a different business component as the primary business component for this business object, then you must make sure the link or join information that is defined for this business component is removed or corrected. If you do not do this, then an error might result.

For more information about:

Siebel Business Process Framework: Workflow Guide Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.