Tools available from the palette for client-side human services
Learn about the tools that are available when you are building client-side human services.
When you are building a client-side human service, the following tools are available from the palette.
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 from a client-side human 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 in client-side human services. | |
End event | Use an end event to end the service execution.
Each path in a service requires its own end event. 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. |
|
Intermediate event | Use an intermediate event to add either 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.
|