Bookshelf Home | Contents | Index | Search | PDF

Siebel Tools Reference > Logical User Interface Objects Configuration >

Reasons a View Is Not Visible to a User

---

When a view is not visible to the logged-in user, there are the following possible reasons:

• The view does not exist in the .srf file.

  This includes a possible misspelling when the view was registered (Site Map > Application Administration > Views); that is, it does not match the view name in the .srf file. If it matches, compile the .srf file again using the All Projects option (full compile).

• The view is not included in one of the logged-in user's responsibilities.
  • Determine which responsibilities the logged-in user has (Site Map > User Administration > Employees).
  • Determine for each responsibility whether the view is included (Site Map > Application Administration > Responsibilities).
• The view is hidden using personalization rules.

  Determine this under Personalization Administration > Views. For testing purposes, you can also switch off the EnablePersonalization parameter in the .cfg file.

• The view is not included either in the menu or in the view tabs. In this case, the view can only be accessed by drilling down from another view.
  • In Siebel Tools, examine the Screen Menu property of the View object. It must be set to TRUE for the view to be included in the Site Map.
  • Determine whether the view is included in a screen and that the Viewbar Text property of the Screen View child object of the screen is set appropriately.
  • Determine whether the view's Visibility Applet and Visibility Applet Type properties are set correctly. For more information, see Creating Views Using the Object Explorer.
• The view belongs to a screen that is not included in the currently running application.
  • In Siebel Tools, determine whether the screen is included in the application (Screen Menu Item child object of the application).
  • Determine whether the application name is spelled correctly in the .cfg file.
• The view does not belong to the same business object as the screen's default view.

  Make sure that the view is based on the same business object.

  For restrictions on the Screen property, see Object Types Reference.

• The view is not available due to upgrade problems.

  If an upgrade was done, make sure that it was successful by verifying all the log files that were created. The upgrade log files are found in the DBSERVER_ROOT\DB_PLATFORM directory.

• The view is not included in your license keys.

  If none of the previous reasons is responsible for the view not being visible, it is likely that the view is not included in your license keys. Send the license keys to Siebel Expert Services for examination. See also Alert 0041 on Siebel SupportWeb.

• The screen menu item or page tab is not translated into its target language.

  Make sure that for each screen associated with the application (Screen Menu Item object) there is a translated string available in the target language and a Screen Menu Item Locale child object. If not, the screen will not appear in the Site Map.

  Similarly, for a page tab to appear, the Page Tab object must have a translated string and a Page Tab Locale child object with the appropriate language code.

  For example, if the application runs in Norwegian, there must be Screen Menu Item Locale and Page Tab Locale objects with the Language Code property set to NOR.

Bookshelf Home | Contents | Index | Search | PDF