Configuring Siebel Business Applications > About Views, Screens, and Applications > About Screens >

Guidelines for Creating a View

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

• Use the guidelines for configuring access control. For more information, see Siebel Security Guide.
• Do not associate a view with more than one screen. If you do this, then problems with the Thread Manager might occur. When Siebel CRM saves a thread in the session file, it stores the name of the view without the name of the associated screen. If the user chooses a thread that navigates to a duplicate view, then Siebel CRM always navigates the user to one screen, even if it created the thread in the other screen. If you define the duplicate view as the default view on both screen tabs, then the user experiences an anomaly in the Siebel client. Siebel CRM chooses one screen tab as the active tab. It never displays the duplicate screen tab as an active tab. For more information, see Configuring the Thread Bar.
• Do not modify a view that Siebel CRM displays in the Administration - Server Configuration screen or in the Administration - Server Management screen. Siebel CRM reads information in these views from the siebns.dat file. The Server Manager displays these views in the Siebel client. Any modification that you make to one of these views must be stored in siebns.dat file. You cannot store this information in siebns.dat. Siebel CRM does not support modifying a server view.
• Due to the specialized nature of the code that the Siebel calendar references, Siebel CRM does not support modification to the following views:
  • HI Activity Calendar View
  • eCalendar Daily View
  • eCalendar Weekly View
  • eCalendar Monthly View

    Oracle supports usage of Siebel Tools to modify the eCalendar Detail View. For more information, see Caution About Using Specialized Classes.

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

Table 26 describes guidelines for naming a view according to the type of view.

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

Table 27 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.