Siebel Business Process Framework: Task UI Guide > Task UI Concepts > UI Elements Used in Task UI >

Task Applet

A task applet differs from standard applet in that it is designed to interact with transient data (data that is transitory during the execution of a task) in fields of transient business components, rather than with standard fields in a regular business component.

Configuring a task applet is part of the larger process of creating tasks for implementing a business process framework. For more information about the procedures involved in configuring a task applet, see Configuring Task UI. See also Creating Task Applets Using the Task Applet Wizard. For more information on transient data binding, see Transient Business Component.

Task Applets and How They Differ from Standard Applets

A task applet differs from a standard applet in the following ways:

  • A task applet is based on a transient business component. Transient business components are used to display data from a task that is discarded when the task ends — for example, data shown to allow the end user to select values that form the branching condition of a task. Depending on the transient data value selected by the end user, the next task step will vary.
  • A task applet has a specialized frame class, CSSSWEFrameTask.
  • A task applet is always a form applet, not a list applet.
  • A task applet can be based only on grid Web templates. These grid Web templates differ from standard Web templates in that they do not display the applet title or the applet menu. A standard applet, particularly the form applet, can be based either on the available standard templates or on grid Web templates.

For more information on how task applets differ from traditional Siebel applets, see Configuring Task Applets.

Siebel Business Process Framework: Task UI Guide Copyright © 2006, Oracle. All rights reserved.