Configuration Guidelines > Creating and Modifying Objects > Configuring Applets >

Creating and Modifying Applets

During the initial stages of an implementation, you define the required views. The applets displayed on these views usually fall into one of these categories:

NOTE:  Remember to set the Upgrade Ancestry property on all custom applets that are cloned from another applet.

Modify, rather than copy, an applet, unless you are making extensive modifications to the applet. This avoids having to change all references of that applet to the new copy.

The following are examples of situations in which you might need to copy an applet:

NOTE:  Do not change the Class property of preconfigured applets.

The objective of your design and configuration projects should be to produce a consistent and intuitive user interface. Wherever possible, applets displaying the same business component should be consistent across different screens and views. For example, the contact list displayed for an opportunity should be consistent with the contact list displayed for an account. Whenever possible, reuse applet definitions between different views and screens. Obvious exceptions include redundant controls or list columns and controls, or list columns that are relevant only to the current parent business component. For example, you would display the contact's account information when displaying opportunity contacts, but not when displaying account contacts. This recommendation does not necessarily apply when comparing list with form or entry applets. When the screen space for a view is limited, it may be practical to include fields at the end of a list applet that are not displayed on the associated entry applet.

Another approach to increasing the number of fields available in a form applet is to use applet toggling. You can define two applets based on the same business component to show information from the same record (but the field controls are distributed over multiple applets) and the user can toggle between the two.

 Configuration Guidelines 
 Published: 18 April 2003