Detail views
You use a detail view to display a selection of attribute information for a particular instance of a resource and also to allow the user to change attribute values.
You can opt to display the information in one or two columns. Two-column detail views increase the amount of data that can be displayed on your screen and reduce the need for screen scrolling. Each column includes the attribute name, the attribute value, and an optional annotation. See Creating a two-column detailed view for guidance on creating a two-column view.
- A read-only, textual representation of the attribute value.
- A modifiable field, so that the user can enter another value.
- A graphical representation of the attribute value.
The optional annotation text appears next to the attribute value and can be used to provide additional information, such as names, valid values, and warnings.
It is advisable to keep the annotation text short, otherwise the contents of the detail view may become less clear.
You can include white space (blank lines) in a detail view to separate groups of attributes. You may also include static text that can be used to provide titles for groups of related attribute fields, or to form explicitly labeled links to other views.
A detail view can be used to provide information for the user, but you can also use a detail view to implement a SET action, allowing the user to change one or more attributes for the selected instance of the managed object.
You can link from a detail view to one or more detail or tabular views, depending on the task you want the user to perform. For example, from a detail view of a task resource, you could link to other detail views showing clock settings, terminal details, and so on. See Components of a view for details of how you might do this.
You can add buttons to a detail view that perform an action immediately, or you can choose to display a confirmation panel. See Confirmation panels for details.
- Make this detail view the default view for the view set. If you select this option, this view will be used for view links that do not target a specific view within the view set. See Default views for information about default views.
- Choose whether the automatic refresh option will be available for this view.
- In the case of views related to definitional objects, choose whether or not to include a Map button in order to generate a map of associated definitions. See How to map CICSPlex SM definitions for information about the map function.