The following topics contain reference information for
Coaches and Coach Views.
The view object
A view is a self-contained runtime JavaScript object that
can render itself in a browser.
The context object
The Coach View context object provides access to helper
functions, for example a callback to fire a named boundary event.
Event handlers
Coach Views have predefined event handlers that perform
callback functions when an event is detected. You can add your own
code to these event handlers in the Behavior page of the Coach View.
Generating URLs of managed assets
Managed assets are images, style sheets, AMD modules or
other assets that are part of a Coach View, but are developed outside
of Process
Designer. To access these assets from a Coach, you might
need use a global JavaScript function to generate the URL of the asset.
For example, to get the URL of an AMD module which is contained in
a zip file.
Generating a unique ID for a coach view
In some situations you might want to use the ID attribute
for your DOM elements within a coach view. However, all DOM IDs must
be globally unique. For example, during collaboration the default
highlighting behavior is implemented based on a unique DOM ID. To
ensure a unique ID, you can use the $$viewDOMID$$ placeholder
keyword. At run time, this keyword will be replaced by the Coach View
DOM ID.
Framework managed versus view managed content for coaches
At run time, the content inside a content box of a coach
can be managed by the runtime framework, or by the view. By default,
the framework manages the content, but if you want to code your own
custom behavior, you can choose that the content be managed by the
view.