Bookshelf v7.5: Creating and Modifying Views

Configuration Guidelines > Creating and Modifying Objects > Configuring Views >

Creating and Modifying Views

During the initial stages of an implementation, you define the required views. These views are usually in one of these categories:

Views that are standard and do not need to be modified.

Views that closely align with an existing view and require the same applet layout, but require other configurations such changing a title, inactivating or adding controls or list columns, and changing display labels. For this category, it is also recommended that you configure the existing view object. Most configurations in this category are actually done on the applets instead of the views.

Views that closely align with an existing view but require a moderately different applet layout, possibly displaying applets based on new business components or adding toggles. For this category, it is also recommended that you configure the existing view object. The design may also require configuration of the existing view applets.

Views that consolidate two already existing views. For this category, it is recommended that you configure one of the existing views by modifying the view object, and remove visibility to the redundant view using the Responsibility Administration screen.

Views that do not have an obvious preexisting equivalent view. These are views that expose new functionality specifically configured for your implementation, exposing new business objects or business components. For this category, it is recommended that you create a new view object and avoid extensively modifying an existing definition that will not be used in your implementation. The resulting configurations will be much cleaner and easier to maintain and upgrade (both manually and automatically).

A view can be associated with more than one screen, but this configuration 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.