1. Business Process Framework: Task UI Guide
  2. Creating a Transient Business Component

Creating a Transient Business Component

If your task requires transient data, then you must create a transient business component. It is strongly recommended that you use the Transient Business Component Wizard to create a transient business component. For more information, see Overview of Transient Data.

To create a transient business component

  1. Determine if your task requires a transient business component.

    If a transient business component is not required by your task, then quit this procedure. For more information, see Determining When to Use a Transient Business Component.

  2. Start the New Object Wizards (click the magic wand icon), go to the Task tab and create a new Transient Business Component.

  3. Configure the properties shown in the following table for the new transient business component.

    Property Description

    Project

    Choose a value from the drop down list. The wizard only lists projects that are locked.

    Name

    Enter a text string that describes the task.

    MultiRecord TBC checkbox

    (Optional) If you are creating a multirecord transient business component, then make sure the MultiRecord TBC option includes a check mark. For more information, see About the Multirecord Transient Business Component.

  4. Click Finish.

    The wizard automatically does the following:

    • Assigns the transient business component to the S_TU_LOG table.

    • Sets the Type property of the business component to Transient.

    • Displays a new record for the transient business component in the Business Components list.

  5. Create a new Field for the Transient Business Component.

  6. Configure the following properties for the new field you created in the previous step:

    • Name

    • Type

    • Text Length

    Caution: The Type property is a required property. The Text Length property is not a required property. However, it is recommended that you define a value for the Text Length property so that Siebel CRM can accurately determine the size of the Column property. If a field of type DTYPE_TEXT includes an undefined text length, then Siebel CRM uses a length of 255 characters. If the actual length is shorter than 255 characters, and if you do not define the Text Length property, then Siebel CRM might create an unnecessary join to an extension table, or even fail to map the field to the correct corresponding column.

    Note the following:

    • The Column property is set automatically.

    • The Column and Join properties are read only.

    • You cannot define a multivalue field.

    • The Task UI framework allows a calculated field. It does not assign a column to a calculated field.

  7. Repeat step 5 and 6 for each additional field you want to define.