Configuring Siebel eBusiness Applications > Overview of Configuring Siebel Applications > About Configuring Siebel Applications >

Guidelines for Naming Objects

When naming objects consider the following:

• Never include a question mark at the end of a field name or user interface label.
• Use meaningful, descriptive object names (for example, Account Detail Applet With Agreement, instead of Account Detail Applet 2).
• Be careful about spelling, spacing, and capitalization when naming objects. Typically, logical names of objects in the repository use complete words, mixed casing, and spaces between words. However, physical database objects use abbreviations, uppercase, and underscores. For example, the Service Request business component is based on the S_SRV_REQ database table.
• It is time-consuming to change an object's name after it has been referenced throughout the repository. If you need to change the name of an object that may have many references throughout the repository, use the Find in Repository feature (from the Tools menu in Siebel Tools) to find all of the references.

TIP:   If you are in doubt about object names, use the existing objects in the standard Siebel repository as your guide. For example, when creating a new Association applet, you would notice the <BusComp> Assoc Applet naming convention. Examine the standard objects and conform to their established naming conventions.

For naming conventions for specific object types, see the following topics:

About Tables

Guidelines for Configuring Business Components

Guidelines for Configuring Joins

Guidelines for Configuring Business Objects

Guidelines for Configuring Applets

Guidelines for Configuring Views