com.google.cloud.dialogflow.cx.v3

Interface Form.Parameter.FillBehaviorOrBuilder

All Superinterfaces:

com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder

All Known Implementing Classes:

Form.Parameter.FillBehavior, Form.Parameter.FillBehavior.Builder

Enclosing class:

Form.Parameter

public static interface Form.Parameter.FillBehaviorOrBuilder
extends com.google.protobuf.MessageOrBuilder

Method Summary

Modifier and Type	Method and Description
Fulfillment	getInitialPromptFulfillment() Required.
FulfillmentOrBuilder	getInitialPromptFulfillmentOrBuilder() Required.
EventHandler	getRepromptEventHandlers(int index) The handlers for parameter-level events, used to provide reprompt for the parameter or transition to a different page/flow.
int	getRepromptEventHandlersCount() The handlers for parameter-level events, used to provide reprompt for the parameter or transition to a different page/flow.
List<EventHandler>	getRepromptEventHandlersList() The handlers for parameter-level events, used to provide reprompt for the parameter or transition to a different page/flow.
EventHandlerOrBuilder	getRepromptEventHandlersOrBuilder(int index) The handlers for parameter-level events, used to provide reprompt for the parameter or transition to a different page/flow.
List<? extends EventHandlerOrBuilder>	getRepromptEventHandlersOrBuilderList() The handlers for parameter-level events, used to provide reprompt for the parameter or transition to a different page/flow.
boolean	hasInitialPromptFulfillment() Required.

Methods inherited from interface com.google.protobuf.MessageOrBuilder

findInitializationErrors, getAllFields, getDefaultInstanceForType, getDescriptorForType, getField, getInitializationErrorString, getOneofFieldDescriptor, getRepeatedField, getRepeatedFieldCount, getUnknownFields, hasField, hasOneof

Methods inherited from interface com.google.protobuf.MessageLiteOrBuilder

isInitialized

Method Detail

hasInitialPromptFulfillment

boolean hasInitialPromptFulfillment()

 Required. The fulfillment to provide the initial prompt that the agent
 can present to the user in order to fill the parameter.
 

.google.cloud.dialogflow.cx.v3.Fulfillment initial_prompt_fulfillment = 3 [(.google.api.field_behavior) = REQUIRED];

Returns:

Whether the initialPromptFulfillment field is set.

getInitialPromptFulfillment

Fulfillment getInitialPromptFulfillment()

 Required. The fulfillment to provide the initial prompt that the agent
 can present to the user in order to fill the parameter.
 

.google.cloud.dialogflow.cx.v3.Fulfillment initial_prompt_fulfillment = 3 [(.google.api.field_behavior) = REQUIRED];

Returns:

The initialPromptFulfillment.

getInitialPromptFulfillmentOrBuilder

FulfillmentOrBuilder getInitialPromptFulfillmentOrBuilder()

 Required. The fulfillment to provide the initial prompt that the agent
 can present to the user in order to fill the parameter.
 

.google.cloud.dialogflow.cx.v3.Fulfillment initial_prompt_fulfillment = 3 [(.google.api.field_behavior) = REQUIRED];

getRepromptEventHandlersList

List<EventHandler> getRepromptEventHandlersList()

 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-<N>`, where N can be from 1 to 6
 *   `sys.no-match-default`
 *   `sys.no-input-<N>`, 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.
 

repeated .google.cloud.dialogflow.cx.v3.EventHandler reprompt_event_handlers = 5;

getRepromptEventHandlers

EventHandler getRepromptEventHandlers(int index)

 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-<N>`, where N can be from 1 to 6
 *   `sys.no-match-default`
 *   `sys.no-input-<N>`, 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.
 

repeated .google.cloud.dialogflow.cx.v3.EventHandler reprompt_event_handlers = 5;

getRepromptEventHandlersCount

int getRepromptEventHandlersCount()

 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-<N>`, where N can be from 1 to 6
 *   `sys.no-match-default`
 *   `sys.no-input-<N>`, 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.
 

repeated .google.cloud.dialogflow.cx.v3.EventHandler reprompt_event_handlers = 5;

getRepromptEventHandlersOrBuilderList

List<? extends EventHandlerOrBuilder> getRepromptEventHandlersOrBuilderList()

 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-<N>`, where N can be from 1 to 6
 *   `sys.no-match-default`
 *   `sys.no-input-<N>`, 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.
 

repeated .google.cloud.dialogflow.cx.v3.EventHandler reprompt_event_handlers = 5;

getRepromptEventHandlersOrBuilder

EventHandlerOrBuilder getRepromptEventHandlersOrBuilder(int index)

 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-<N>`, where N can be from 1 to 6
 *   `sys.no-match-default`
 *   `sys.no-input-<N>`, 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.
 

repeated .google.cloud.dialogflow.cx.v3.EventHandler reprompt_event_handlers = 5;