Determining When to Use a Transient Business Component

This topic describes how to determine whether to use a transient business component or not.

If one of the following situations is true, then you must use a transient business component. If none of these situations are true, then do not need to use a transient business component. Use a business component instead.

• A radio button or decision point determines the task flow.

• The task must temporarily store data. For more information, see Storing Data Temporarily While Gathering the Information Required to Create a Complete Record.

• You cannot use the Defer Write Record property to store transient data. For more information, see Using the Defer Write Record Property of a Siebel Operation Step Instead of a Transient Business Component.

• You must control a search specification. For example, if a user must make a choice that includes a predefault value, such as in reply to the following question:

  In what month did the transaction occur?

• If a task must modify transient data while the task runs:

  • To use fields from different business components in a single applet. For example, to allow the user to create a new account and enter contact data in a single task applet.

  • To modify the appearance of the user interface depending on run-time conditions. For example, according to a choice that the user makes, UI controls can map to different fields of a business component. If the user chooses Credit Card as a payment method, then fields for credit card type, number, and expiration date are available at run time.

  • To determine if a record already exists before committing a new record that might be a duplicate.

For more information, see Creating a Transient Business Component.