|
Siebel Business Process Framework: Task UI Guide > Developing a Task UI > Developing a Task UI That Uses Transient Data >
About the Multirecord Transient Business Component
A multirecord transient business component is a type of transient business component that can include more than one record for a given task UI context. The following examples describe situations where you might use a multirecord transient business component:
- To allow the user to choose a single record from several records during the course of completing a task UI. For example, the user might create several plans but near the end of the task UI choose the plan that most closely matches the business requirement. While the task runs, Siebel CRM saves each plan as a separate record in the multirecord transient business component. It saves only a single record to the Siebel database after the task finishes.
- To automate the creation of records for a merge. For example, assume your deployment must automate record creation for a merge. This operation is similar to mimicking a three way merge where Siebel CRM automatically creates three records for a user, and then asks the user to choose the record that it must resolve. The record that the user chooses is the only record that it saves to the Siebel database. It clears the remaining records.
A multirecord transient business component can do some of the same operations that a standard business component can do, such as insert, update, delete, copy, or undo. You can use a multirecord transient business component in a Siebel operation step in the same way that you use a standard business component. Siebel CRM clears the records in a multirecord transient business component when the task UI finishes or if the user cancels it. If the user pauses the task, then these records remain in temporary storage. Classes That Siebel CRM Uses with a Transient Business Components
Table 15 describes classes that Siebel CRM uses with a single record transient business component and with a multirecord transient business component. The default setting is single record. If you create a transient business component, then it is strongly recommended that you use the New Business Component Wizard to make sure that you properly define the CSSBCTaskTransient class, the CSSBCTaskTransientBase class, or a class that Siebel CRM derives from these classes.
Table 15. Classes That Siebel CRM Uses With a Transient Business Component
|
|
|
Single record transient business component |
Supports a single record in a task UI context. |
Uses the CSSBCTaskTransient class or a class that Siebel CRM derives from the CSSBCTaskTransient class. The CSSBCTaskTransient class makes sure only one row exists for each context for each single record transient business component. The context of a transient business component resides at the level of the subtask. This means that even if a subtask uses the same single record transient business component with the parent task, then the two subtasks do not share the same transient business component record. This specialized CSSBCTaskTransient class also filters the single record for the current context and the current business component. It runs a default query on the first Get function or Set function, and it creates a new record if no such record exists. That is, if the following method returns no rows: Execute
|
Multirecord transient business component |
Supports multiple records in a task UI context. |
Uses the CSSBCTaskTransientBase class or a class that Siebel CRM derives from the CSSBCTaskTransientBase class. |
|
