You can define the data used by the coach view and the
ways in which users can configure it.
Procedure
Define the variables that the coach view uses to store
its association with business data and how users can configure the
coach view in its Variables page.
- To associate the coach view with data, add data such as
a business object. A coach view can have only one associated
data object. A data association is not mandatory. The coach views
that this coach view contains can bind to the associated data object
or one of its parameters if it is a business object.
Restriction: To avoid errors with binding a map to an instance
of the coach view, use a list (array) of NameValuePair instead
of a business data variable with the map type. This ensures that the
variable and its properties are all typed, and can be understood by
the server.
- To provide users with ways to customize coach view instances,
add configuration options. Coaches and coach views that
contain your coach view display these options as configuration properties
when users select your coach view in the layout. The users can then
configure the instance by using the options that you provided.
For example, the Button stock control has the allowMultipleClicks configuration
option. If you put a Button instance into a coach view, you can see Allow
multiple clicks when you view its properties.
For
service types, you must specify a default service to identify the
signature of the service.
- To provide translations for the
text of your coach view, add resource bundles by adding localization
resources. For information, see Localizing user interfaces.