Configuring Siebel Business Applications > About Applets, Controls and List Columns >

Guidelines for Creating an Applet

This topic describes guidelines for creating an applet. It includes the following topics:

• Guidelines for Naming an Applet
• Guidelines for Creating a Check Box

If you create an applet, then use the following guidelines:

• Keep the user interface consistent and intuitive.
• To reduce complexity, keep applet design simple.
• Avoid inactive objects.
• If possible, modify a predefined applet instead of creating a new applet. This configuration often requires less work and helps to minimize the objects that reside in the Siebel repository that you must maintain. For more information, see Guidelines for Reusing an Applet.
• To avoid unnecessary duplication, reuse an applet in multiple views and screens.
• If you do require a new applet, then set the Upgrade Ancestor property on each custom applet that you define from another applet. For more information, see Guidelines for Setting the Upgrade Ancestor Property.
• Define the applet mode:
  • If the applet is in read-only mode, then you only define it in Base mode.
  • If the applet is editable, then you must define it in Edit and Edit List modes.
• Do not display a field that no applet uses.
• You cannot add a user interface control in the column of a list applet. Buttons, picklists, and fields are examples of user interface controls.