Siebel Business Process Framework: Task UI Guide > Guidelines and Techniques for Developing a Task UI > Techniques to Improve the Usability of a Task UI >

Mixed Applet Technique


If a task UI must display data from several business components in a single applet, then you can create a task UI that uses a transient business component to hold data for the mixed applet. The task UI can save the data to a nontransient business component. The task UI saves this data immediately following the view that includes the mixed applet. For more information, see Overview of Transient Data.

Example of the Mixed Applet Technique

The predefined CMEREF - Activation Order task UI is an example of the mixed applet technique. It asks for the following information in a single applet:

  • Account name
  • Customer first name
  • Customer last name

At a later point in this task UI, it uses this data to query an existing account and contact. If it does not find a record, then it does one the following:

  • Creates a new account or a new contact
  • Creates a new account and a new contact
Siebel Business Process Framework: Task UI Guide Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.