Siebel Business Process Framework: Task UI Guide > Customizing Task UI > Other Options for Customizing a Task UI >

Reusing a Standard Applet


If the applet you use in a task UI does not interact with transient data, then, as an option, you can copy and modify a standard, predefined applet instead of creating a new one. For more information, see Overview of Transient Data.

To reuse a standard applet

  1. Identify a standard applet:
    1. In the Siebel client, examine the Siebel application for an applet that closely matches your display requirements.
    2. Locate a candidate applet.
    3. Choose the Help menu, and then the About View menu item.
    4. Note the value in the Applets section.

      If Siebel CRM lists more than one applet, then note the applet name that most closely matches the functionality of the candidate applet.

    5. In Siebel Tools, query the Name property of the Applets list for the applet you identified in Step b.
    6. In the Applets list, right-click, and then choose Edit Web Layout.
    7. Verify that the layout resembles the applet you identified in Step b.'
    8. Close the Web Layout Editor.
  2. Copy a standard applet:
    1. In the Applets list, right-click, and then choose Copy Record.

      Siebel Tools performs a cascade copy of the applet. You can view the status bar that Siebel Tools displays along the bottom of the Siebel Tools user interface to monitor the status of the copy operation. Siebel Tools finishes the copy, and then displays the new record in the Applets list and places the cursor in the Name property.

    2. In the Name property, enter a name for your custom applet that indicates how the user uses the applet.

      For example, Account Entry for task UI.

    3. If necessary, define the Project property.
    4. In the Applets list, right-click the applet, and then choose Edit Web Layout.
    5. In the Applet Web Template window, delete unnecessary controls.

      Task UI is intended to simplify the user interface, so it is recommended that you remove controls and labels that the user does not require to finish the task. Make sure you do not delete fields that the user requires to finish the task. For example, an insert operation for an opportunity requires the following fields:

      • Opportunity Name
      • Close Date
      • Currency
    6. In the Applet Web Template window, reposition controls and their labels until the applet resembles the required layout for the task UI.
    7. Save your work, and then close the Applet Web Template window.
Siebel Business Process Framework: Task UI Guide Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.