Behavior if an exception occurs during ControlHandler.canHandle.
In all cases, ControlManager.handleInternalError
will be called. The options
differ in how the response is produced.
ProduceResponse (default) - treat the input as handled, and return the custom response
ReturnFalse - treat the input as 'cannot handle'.
Rethrow - let the exception bubble up to be processed by CustomSkill.errorHandlers
Usage:
Determines if the controls state will be correctly reestablished on the next turn
Usage:
validateStateRoundtrip = false
.Determines if this RequestHandler handle the input.
HandlerInput
Handle the input.
HandlerInput
Take the initiative in the dialog.
Any existing content in the Response's prompt & reprompt is overwritten. To avoid losing this content, pass it in using parameters promptPrefix & repromptPrefix.
Usage:
RequestHandler
into
Controls For example, when a regular RequestHandler
consumes the
input but doesn't want to keep the initiative, it can ask a
ControlHandler to take the initiative to complete the turn. A
prompt/reprompt fragment can be specified by the RequestHandler
which will be included as the start of the overall prompt/reprompt.Handler input
Prompt fragment to prefix the prompt generated via Controls.
Reprompt fragment to prefix to the prompt generated via Controls
Creates a string 'C:
The information gathered is only the number of Controls being used. This will help the dev team to understand usage - thank you!
Implements the core of the processing loop
Public for testing
RequestHandler for a skill built using Controls.
This is the common runtime that drives the processing flow for a skill that uses Controls. Please see the user guide for a thorough discussion of the phases of processing and how the common
ControlHandler
interfaces with an instance ofControlManager
and the control tree.