Tools available from the client-side human services palette

Learn about the tools that are available when you are modeling client-side human services.

When you model a client-side human service, the following tools are available from the palette.

Table 1. Tools available from the palette for client-side human services

Icon	Tool name	Description
	Coach	Use a coach to implement the user interfaces that are displayed when you run the client-side human service. For more information, see Building coaches.
	Client-side script	Use a client-side script when you want to add JavaScript code to run on the web browser in the client-side human service context, for parsing variables, and running programmatic commands.
	Service	Use a service to call another service from within a client-side human service. The called service adds an activity to the service flow, which calls another service that you can specify. The called service cannot be another client-side human service or a heritage human service. For more information, see Calling another service.
	Exclusive gateway	Use an exclusive gateway to model a point in the flow execution where only one of several paths can be followed, depending on a condition. For more information, see Implementing exclusive gateways.
	End event	Use an end event to end the service execution. Each path in a service requires its own end event. End event Use an end event to complete the processing of the service flow. An end event is automatically included each time you create a service. For more information about modeling end events in client-side human services, see Navigation options for after service completion. Error end event Use an error end event to throw an error and end the processing of the service flow. To throw a specific error, you can set the error properties in the Implementation tab of the error end event, by specifying the error code and mapping the error end event to a specified variable. For more information, see Handling errors in client-side human services.
	Intermediate event	Use an intermediate event to add a stay-on-page event, a postpone event, or an error boundary event to the service flow. You can specify the event type in the Implementation tab of the intermediate event. The default implementation uses the stay-on-page event. Stay on page Use a stay-on-page event to loop the service flow back to the previous running coach without drawing a connection to it. The stay-on-page event returns the control back to the coach, so that any variable updates made since the boundary event for the coach are refreshed on the same user interface page. For an example, see Using client-side validation. Postpone Use a postpone event to postpone work on a specified task for later completion. The postpone event halts the execution of the task and keeps the task in a suspended state until it can be resumed at a later moment. This event can be used only with client-side human services that implement tasks within a BPD or case type. For more information, see Enabling work to be postponed and resumed at run time. Error intermediate event Use an error boundary event to catch errors and receive error data from the service to which it is attached. In a client-side human service, you can attach an error boundary event only to a service in the human service flow. For more information, see Handling errors in client-side human services.
	Event handler	Use an event handler to add a subflow that is triggered by one of the following types of events. By default, the subflow is triggered by an error event. Error event The subflow is triggered by an error event. Use an error event handler to add global error handling to a client-side human service. Data change event The subflow is triggered by a data change on the server. Use a data change event handler to control the refresh behavior of an instance details or task UI. A client-side human service can have only one data change event handler.
	Note	Use a note to provide additional textual information to a client-side human service diagram. You can add reminders, development notes, or information that is relevant to a specified step in the service flow. The notes can be added to the canvas as stand-alone objects or can be connected to specified nodes in the diagram. For more information, see Adding notes.