Guidelines for Naming an Object
If you name an object, then use the following guidelines:
Never include a question mark at the end of a field name or user interface label.
Use an object name that is meaningful and descriptive. For example, Account Detail Applet With Agreement, instead of Account Detail Applet 2.
Do not use a license key option as an object name. For example, do not use Product Forecasting. This configuration can cause Siebel CRM to not display a user interface object, such as a view.
Prefix the name for each custom object that you create with your company name. For example, ABC Product Forecasting View. This configuration distinguishes your custom object from a predefined object.
Be careful with spelling, spacing, and capitalization when you name an object. Typically, the logical name of an object in the Siebel repository uses complete words, mixed casing, and a space between words. A physical database object might use an abbreviation, uppercase, and an underscore. For example, the Service Request business component references the S_SRV_REQ database table.
Do not use a reserved SQL word in an object name. For example SELECT, COUNT, FROM, WHERE, and UNION. This configuration can cause unpredictable application behavior.
Avoid modifying the name of an object. It is time consuming to modify the name of an object when Siebel CRM references it throughout the Siebel repository. If you must modify the name of an object, then use the Find in Repository feature from the Tools menu in Siebel Tools to find all of the references.
Siebel Tools uses English (ENU). It does not support objects from other character sets, such as ASCII (American Standard Code for Information Interchange) codes or accented characters. If you attempt to use objects from another character set, then Siebel Tools displays a unique constraint error.
If you are not sure how to name an object, then you can use the predefined objects in the Siebel repository as a guide. Examine the predefined objects and conform to the naming formats that they use. For example, to create a new Association applet, use the business component name Assoc Applet naming format.
For more information, see the following topics: