Guidelines for Naming a View

If you name a view, then use the following guidelines:

• Use a prefix that identifies your company. For example, name a new view for ABC Incorporated as ABC Opportunity Detail - Tasks View.

• Make the view name meaningful. Avoid adding a number suffix to a predefined name, such as Opportunity List View 2.

• If the view differs because it is read-only, then indicate that it is read-only. For example, ABC Opportunity List View - Read Only.

• Capitalize the first letter of each word. For example, Opportunity List View rather than opportunity list view.

• Do not use a special character, such as an ampersand (&).

Guidelines for Naming a View According to the Type of View

The following table describes guidelines for naming a view according to the type of view.

Type of View	Name Format	Example
List-form view	business component List View	Account List View
Master-detail view	detail business component Detail - master business component View	Opportunity Detail - Contacts View
Explorer view	business component Explorer View	Account Explorer View
Chart view	master business component Chart View - detail business component Analysis	Account Chart View - State Analysis

Guidelines for Naming a View According to the Type of Aggregate View

The following table describes guidelines for naming a view according to the type of aggregate view. The text in italics indicates the text that Siebel CRM modifies according to the underlying entity. For more information, see Guidelines for Naming an Object.

Type of Aggregate View	Example
Personal	My Personal Contacts
Sales Rep	My Contacts
Manager	My Team’s Contacts
Organization	All Contacts
Sub Organizations	All Accounts Across My Organizations
All	All Contacts Across Organizations
Group	User Catalog List View
Catalog	Products Across Catalogs
Admin Mode	Contacts Administration