Foglight 5.9.7 - Web Component Guide

Additional Context for a View

Additional Context for a view allows you to supply additional information that your view can use inside its configuration or additionally, if it is a container view, for use by its children.

If you know that you are going to refer to a particular child of an existing context key often, you can create a new key that shortcuts the reference. For example:

agent = <host>/agent, where host is an object that has a property called agent.

This is also useful if you are building a container view and want to include children that require particular keys that are not explicitly present. Example: the child view has a key called host, but your parent view uses selectedHost. Solution: in additional context, map host to selectedHost. This section needs work. Find out what “a particular child of an existing context key” is, and what is meant by keys that are not explicitly present. The text above comes from the Wiki.

Additional Context for an Instance

When adding a view to a container view, it sometimes happens that the available context does not have the right information for the view that you want to include. In this case, it is possible in the container view to selectively create the right context. This is called additional context for an instance or instance context. The context is for that particular instance of the view and is not available when you use the view somewhere else. It would be more useful to show where to set the additional context, and to give an illustrative example.

NOTE: You would create the additional context of the view itself if you wanted it available to every instance of the view.

Additional Context for a Flow

The progression from one view to another is called a flow. How the new view is made to appear depends on the flow action. The types of flow actions are described in Flow Types .

Often these views may have input requirements that exceed what is available in the context of the component from which you are coming. In this case, it is possible to define further Additional Context that applies to the flow. An illustrative example would be good here too.

Dynamic Context

Dynamic context keys are supplied by the component itself, and the value usually depends on some action taken by the end user. Dynamic context is only available for some components, such as Bar or Pie Chart, Cluster Bar Chart, Time Bar Chart, Time Plot Chart, Drop-Down List, Filter, Radio Button List, Row-Oriented Table, Tree Table, and Topology. The value of a dynamic context item changes depending on what is being rendered at the time, such as a row in a Row-Oriented table, or what is being selected, such as an item in a list. For example, in the Row-Oriented Table the dynamic context key current Row is available. When a row is processed for display, that row’s current Row value changes depending on which row is currently being rendered. Similarly, when an action is defined for row selection on a table, the selected row’s current Row value can be passed to the target of the action.

Dynamic context keys are not taken into consideration when the tree of views available for next page or popup flow types are filtered. Thus, they are essentially not available to be used as inputs for other views, they are just available for internal references when a view is being rendered.

Examples of dynamic context keys are:

There are other components that have properties associated with dynamic context keys. See the Web Component Reference pages for details.