GetFlowResult

data class GetFlowResult(val description: String, val displayName: String, val eventHandlers: List<GoogleCloudDialogflowCxV3EventHandlerResponse>, val name: String, val nluSettings: GoogleCloudDialogflowCxV3NluSettingsResponse, val transitionRouteGroups: List<String>, val transitionRoutes: List<GoogleCloudDialogflowCxV3TransitionRouteResponse>)

Constructors

Link copied to clipboard
fun GetFlowResult(description: String, displayName: String, eventHandlers: List<GoogleCloudDialogflowCxV3EventHandlerResponse>, name: String, nluSettings: GoogleCloudDialogflowCxV3NluSettingsResponse, transitionRouteGroups: List<String>, transitionRoutes: List<GoogleCloudDialogflowCxV3TransitionRouteResponse>)

Types

Link copied to clipboard
object Companion

Properties

Link copied to clipboard

The description of the flow. The maximum length is 500 characters. If exceeded, the request is rejected.

Link copied to clipboard

The human-readable name of the flow.

Link copied to clipboard

A flow's event handlers serve two purposes: * They are responsible for handling events (e.g. no match, webhook errors) in the flow. * They are inherited by every page's event handlers, which can be used to handle common events regardless of the current page. Event handlers defined in the page have higher priority than those defined in the flow. Unlike transition_routes, these handlers are evaluated on a first-match basis. The first one that matches the event get executed, with the rest being ignored.

Link copied to clipboard

The unique identifier of the flow. Format: projects//locations//agents//flows/.

Link copied to clipboard

NLU related settings of the flow.

Link copied to clipboard

A flow's transition route group serve two purposes: * They are responsible for matching the user's first utterances in the flow. * They are inherited by every page's transition route groups. Transition route groups defined in the page have higher priority than those defined in the flow. Format:projects//locations//agents//flows//transitionRouteGroups/.

Link copied to clipboard

A flow's transition routes serve two purposes: * They are responsible for matching the user's first utterances in the flow. * They are inherited by every page's transition routes and can support use cases such as the user saying "help" or "can I talk to a human?", which can be handled in a common way regardless of the current page. Transition routes defined in the page have higher priority than those defined in the flow. TransitionRoutes are evalauted in the following order: * TransitionRoutes with intent specified. * TransitionRoutes with only condition specified. TransitionRoutes with intent specified are inherited by pages in the flow.