Siebel Business Process Framework: Task UI Guide > Guidelines and Techniques for Developing a Task UI > Improving the Usability of a Task UI >
Mixed Applet Technique
If data from several business components must be presented in a single applet, then you can define a Task UI that uses a transient business component to hold data for the Mixed Applet. Then your task can move the data to the appropriate nontransient business component as soon as possible. Ideally, the task performs this move immediately following the view that contains the Mixed Applet.
Example of the Mixed Applet Technique
The predefined CMEREF- Activation Order task UI asks for an account name, customer first name, and customer last name in a single applet. Later, this data is used to query an existing account and contact. If no record is found, then a new account or contact record, or both, is generated.