
Configuring Views and Context 107
Configuring Views
When creating a nested view, the Context tab shows allows the user to define additional
context for the nested component. The selected inputs are required in the nested view.
All context inputs of the nested view are read-only.
A context input of a nested view might be converted to optional. This can happen if the
nested view has an action configured that has generated context that is for input which
causes an implicit (optional) context input to be created.
Replacing Views
Since system views are predefined views that are shipped with a WCF-based
application, they may be referred to by other views so the IDs of these system views
should not change. However, if you want to replace a system view with a new view that
is based on a different component, you are not able to edit the view and change its
component type. Instead, you create a new view and then replace the old view with a
reference to the new view.
In order to do this, select the view to be replaced in the Definitions editor, then click the
Remove button. Regardless of whether the view is removable (whether it has
dependents or not), you have the option of replacing the view. If you choose to replace
it, you then see a tree of views that includes only the views that have context inputs that
are compatible with the required context inputs of the view to be replaced. Once the
replace is confirmed, the view that was replaced no longer appear in the Definitions
editor. Any references to it are automatically be converted to refer to the selected
replacement view.
Definitions Pane Settings Tabs
If you have added a new view and are beginning to edit it, or when opening an existing
view, the Definitions pane displays a series of tabs. These tabs enable you to configure
the view definition properties. Each view is defined by a group of settings and each of
these groupings has its own tab in a definition.
Kommentare zu diesen Handbüchern