
Configuring Views and Context 123
Context and the Context Tab
• The Configuration tab in the View editor—by setting a parameter’s value in the
Edit - Value dialog for a component.
• In the Flow tab of the View editor—you can set additional context here, or map
from internal component sources into the context.
For example, a page is designed to display information for a selected host. When you
click a link, the host object is passed to a detail page (in this case, you have already set
up the detail page to require host information when it is called). The detail page uses
that information as its initial context settings. The Context tab is where you set up the
list of required context data. Using a required Context setting means that the page or
view is dependent for its data on that context value being available.
Context Tab
Context allows you to define the list of information that is required for a particular view
to display the data that the page is designed to show. When a context element is defined
it is given a name key and it is assigned a data type.
Global Context
In any application there is global or application level context, which is the information
that is available throughout the application. An example of this type of context is
timeRange. Each application can decide to make arbitrary information available to all
views.
Dashboard Context
Context is implemented so that changes to one context element affect other elements in
a hierarchy. If a context element changes in a nested level, the change traverses up the
hierarchy to the parent level, assuming that an uninterrupted chain of key definitions
exists.
User Context
When a user interacts with views the interaction can cause changes to the context. For
example, when selecting a particular item in a drop down list, by default the Web
Component Framework saves the last known values so that when you return to the page,
it displays with that same item selected.
Note You can disable this behavior in User Preferences.
Komentarze do niniejszej Instrukcji