Bookshelf Home | Contents | Index | Search | PDF |
Configuration Guidelines > Naming Conventions > Naming Conventions >
Business Objects and Business Components
The following general naming conventions apply to business objects and business components:
- Business component and business object names must be unique and meaningful. Avoid naming new business components or business objects by adding a number suffix to an existing name (for example, Account 2). This type of name does not clearly communicate how the new object definition differs from the original one. For example, if you create a new business object to support a unique account screen for your Telesales group, you might call the business object Telesales Account to clearly indicate its intended use.
- Name all new business components and business objects with a prefix that identifies your company. For example, ABC Incorporated could name a new object definition ABC Telesales Account. This approach makes it easy to identify the object definitions in the repository that are not object definitions defined by Siebel Systems. This approach also makes it easy to query for your newly defined object definitions and simplifies upgrading your repository.
Initial-capitalize business component and business object names, for example, Account rather than account. This prevents unexpected sorting behavior in the Object List Editor.
Bookshelf Home | Contents | Index | Search | PDF |
Configuration Guidelines Published: 18 April 2003 |