Configuring Siebel eBusiness Applications > Configuring Screens and Views >

Guidelines for Configuring Views

When configuring views consider the guidelines in the following:

• Review the guidelines for configuring access control in Security Guide for Siebel eBusiness Applications.
• Do not associate views with more than one screen because it will cause the Thread Manager to behave incorrectly. When a thread is saved in the session file, the name of the view is stored without the name of the associated screen. When a user chooses a thread that navigates to a duplicated view, the user always navigates to one screen only, even if the thread was created in the other screen. Additionally, if the duplicate view is defined as the default view on both screen tabs, the user sees an anomaly in the user interface. One screen tab is selected as the active tab when either of the screen tabs are selected. The duplicate screen tab never appears to be active.
• Do not modify Administration - Server Configuration and Administration - Server Management views. Information in these views is read from the siebns.dat file and displayed in the user interface by the Server Manager. Configurations made to these views would also have to be made to the siebns.dat file. However, it is not possible to configure the product to store such information in siebns.dat. Therefore, configuration of server views is not recommended or supported.
• Due to the specialized nature of the code upon which the Siebel calendar is based, configuration of the following views is not supported:
  • High Interactivity Client Calendar View
  • eCalendar Daily View
  • eCalendar Weekly View
  • eCalendar Monthly View

    NOTE:  Configuration of the eCalendar Detail View is supported through Siebel Tools.

Naming Conventions for Views

The following are general recommendations for view naming:

• Name a new view using a prefix that identifies your company. For example, a new view created for ABC Incorporated could be named ABC Opportunity Detail - Tasks View.
• View names should be meaningful. Avoid naming new views by adding a number suffix to an existing name (for example, Opportunity List View 2). If the view differs because it is read-only, then indicate this in your view name (for example, ABC Opportunity List View - Read Only).
• Initial-capitalize view names, for example, Opportunity List View rather than opportunity list view.
• Do not use special characters such as an ampersand (&) when naming the views.

In addition, note the conventions in Table 44 for specific view types.

Typically, you should conform to a standard naming convention when naming views. Table 45 provides examples for each view visibility type. The italicized text identifies examples of the conventions you should use for each type of view visibility when naming views.