class Google::Apis::DialogflowV3beta1::GoogleCloudDialogflowCxV3FormParameterFillBehavior

Configuration for how the filling of a parameter should be handled.

Attributes

initial_prompt_fulfillment[RW]

A fulfillment can do one or more of the following actions at the same time: * Generate rich message responses. * Set parameter values. * Call the webhook. Fulfillments can be called at various stages in the Page or Form lifecycle. For example, when a DetectIntentRequest drives a session to enter a new page, the page's entry fulfillment can add a static response to the QueryResult in the returning DetectIntentResponse, call the webhook (for example, to load user data from a database), or both. Corresponds to the JSON property `initialPromptFulfillment` @return [Google::Apis::DialogflowV3beta1::GoogleCloudDialogflowCxV3Fulfillment]

reprompt_event_handlers[RW]

The handlers for parameter-level events, used to provide reprompt for the parameter or transition to a different page/flow. The supported events are: * ` sys.no-match-`, where N can be from 1 to 6 * `sys.no-match-default` * `sys.no- input-`, where N can be from 1 to 6 * `sys.no-input-default` * `sys.invalid- parameter` `initial_prompt_fulfillment` provides the first prompt for the parameter. If the user's response does not fill the parameter, a no-match/no- input event will be triggered, and the fulfillment associated with the `sys.no- match-1`/`sys.no-input-1` handler (if defined) will be called to provide a prompt. The `sys.no-match-2`/`sys.no-input-2` handler (if defined) will respond to the next no-match/no-input event, and so on. A `sys.no-match- default` or `sys.no-input-default` handler will be used to handle all following no-match/no-input events after all numbered no-match/no-input handlers for the parameter are consumed. A `sys.invalid-parameter` handler can be defined to handle the case where the parameter values have been ` invalidated` by webhook. For example, if the user's response fill the parameter, however the parameter was invalidated by webhook, the fulfillment associated with the `sys.invalid-parameter` handler (if defined) will be called to provide a prompt. If the event handler for the corresponding event can't be found on the parameter, `initial_prompt_fulfillment` will be re- prompted. Corresponds to the JSON property `repromptEventHandlers` @return [Array<Google::Apis::DialogflowV3beta1::GoogleCloudDialogflowCxV3EventHandler>]

Public Class Methods

new(**args) click to toggle source
# File lib/google/apis/dialogflow_v3beta1/classes.rb, line 662
def initialize(**args)
   update!(**args)
end

Public Instance Methods

update!(**args) click to toggle source

Update properties of this object

# File lib/google/apis/dialogflow_v3beta1/classes.rb, line 667
def update!(**args)
  @initial_prompt_fulfillment = args[:initial_prompt_fulfillment] if args.key?(:initial_prompt_fulfillment)
  @reprompt_event_handlers = args[:reprompt_event_handlers] if args.key?(:reprompt_event_handlers)
end