Boundary events

A boundary event acts as a trigger within a human service that sends information from a client to a server where the information is then committed and the human service moves to the next step.

You can use named boundary events in both stock views and custom views; however, only one boundary event can be specified per Coach View. The stock button control views have boundary events specified by default.

When you create a Coach View, you specify a boundary event on the Overview tab under Usage. Add JavaScript code to trigger the event at the appropriate time using the this.context.trigger(callback) application programming interface (API). This code is part of the behavior defined in the Behavior tab of the view.

Important: When a boundary event has been specified in a Coach, the boundary event must be wired to the next state. For loopback scenarios where the data is committed and then the same Coach reopens, only the affected data is reloaded in the Coach View instead of the full page.

Related reference:
The context object

Related information:
Building Coaches
Building a Human service