Views

Because views are reusable, each view instance can share parts of its user interface with other view instances in a coach. For example, you create a coach that contains a view instance that includes a set of address fields. If you create a second coach that needs the same address fields, you can reuse the view. In both cases, the coach is using an instance of the view. You can edit the properties of each instance independently. For example, changing the label of one view instance does not change the label of the other. Both view instances use a reference to point to the view definition. This approach means that if the view definition changes, you can see the change reflected in the instances of the view.

You can modify the view instances by using configuration properties and by overriding default styling. For each view, the data binding is optional. However, if you define a binding for an instance, it must match the type in the view definition. A warning occurs if the business object type does not match the type of the data binding that is defined for the view. In each view topic, the business object binding table lists the business object type that is defined for the view. For each view instance, the configuration properties are optional. If you want to override the default value, you can provide a specific value or you assign a variable. As a convenience, you can also expose the configuration property to any view or coach in a human service that contains the view. Exposing the configuration property creates a configuration option in the current view with matching binding. You do not have to create the configuration option and bind it.