Siebel Business Process Framework: Task UI Guide > Developing a Task UI > Developing a Task UI That Uses Transient Data >
Determining if You Must Use a Transient Business Component
This topic describes how to determine if you must use a transient business component. To determine if you must use a transient business component
- If one the following situations is true, then you must use a transient business component. If the following situations are not true, then do not use a transient business component. Use a business component instead:
In what month did the transaction occur?
- If a task UI 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.
- If you determined in Step 1 that you must use a transient business component, then create one now.
For more information, see Creating a Transient Business Component.
|