To contain functions or user interface elements that another Coach View or a Coach can use, create a Coach View.
Creating a Coach View can be an iterative process in which you do steps 3 - 6 in any order. You might start by following the instructions in the order that is listed in the procedure. Based on the results of your test, update the appropriate pages and retest. Continue the iterative process of updating and retesting until you are satisfied with the look and behavior of your Coach View.
this.context.options._metadata.label.get("value");
For example, the Button stock control has the allowMultipleClicks configuration option. If you put a Button instance into a Coach View and then view its properties, you can see Allow multiple clicks. This configuration property is the label and UI implementation of the allowMultipleClicks configuration option.
For service types, you must specify a default service to identify the signature of the service.
When you drop a Coach View onto the layout, Process Designer automatically selects it and shows its properties.
.widerTextBox .dijitTextBox {
width: 365px;
}
In this .css file, you extended dijitTextBox by
creating widerTextBox to override the default width
of the stock text control. In the layout of the Coach View, you can
then select a text control and add the widerTextBox class
in the HTML Attributes. When you see the text control in a browser,
it has the width that is specified by the class and not the default
width.