Package com.google.cloud.dialogflow.cx.v3beta1

Class Form.Parameter.FillBehavior.Builder

java.lang.Object
com.google.protobuf.AbstractMessageLite.Builder
com.google.protobuf.AbstractMessage.Builder<BuilderT>
com.google.protobuf.GeneratedMessage.Builder<Form.Parameter.FillBehavior.Builder>
com.google.cloud.dialogflow.cx.v3beta1.Form.Parameter.FillBehavior.Builder
All Implemented Interfaces:
Form.Parameter.FillBehaviorOrBuilder, com.google.protobuf.Message.Builder, com.google.protobuf.MessageLite.Builder, com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder, Cloneable
Enclosing class:
Form.Parameter.FillBehavior
public static final class Form.Parameter.FillBehavior.Builder extends com.google.protobuf.GeneratedMessage.Builder<Form.Parameter.FillBehavior.Builder> implements Form.Parameter.FillBehaviorOrBuilder
 Configuration for how the filling of a parameter should be handled.
Protobuf type google.cloud.dialogflow.cx.v3beta1.Form.Parameter.FillBehavior

  • Method Details

    • getDescriptor

      public static final com.google.protobuf.Descriptors.Descriptor getDescriptor()

    • internalGetFieldAccessorTable

      protected com.google.protobuf.GeneratedMessage.FieldAccessorTable internalGetFieldAccessorTable()
      Specified by:
      internalGetFieldAccessorTable in class com.google.protobuf.GeneratedMessage.Builder<Form.Parameter.FillBehavior.Builder>

    • clear

      public Form.Parameter.FillBehavior.Builder clear()
      Specified by:
      clear in interface com.google.protobuf.Message.Builder
      Specified by:
      clear in interface com.google.protobuf.MessageLite.Builder
      Overrides:
      clear in class com.google.protobuf.GeneratedMessage.Builder<Form.Parameter.FillBehavior.Builder>

    • getDescriptorForType

      public com.google.protobuf.Descriptors.Descriptor getDescriptorForType()
      Specified by:
      getDescriptorForType in interface com.google.protobuf.Message.Builder
      Specified by:
      getDescriptorForType in interface com.google.protobuf.MessageOrBuilder
      Overrides:
      getDescriptorForType in class com.google.protobuf.GeneratedMessage.Builder<Form.Parameter.FillBehavior.Builder>

    • getDefaultInstanceForType

      public Form.Parameter.FillBehavior getDefaultInstanceForType()
      Specified by:
      getDefaultInstanceForType in interface com.google.protobuf.MessageLiteOrBuilder
      Specified by:
      getDefaultInstanceForType in interface com.google.protobuf.MessageOrBuilder

    • build

      public Form.Parameter.FillBehavior build()
      Specified by:
      build in interface com.google.protobuf.Message.Builder
      Specified by:
      build in interface com.google.protobuf.MessageLite.Builder

    • buildPartial

      public Form.Parameter.FillBehavior buildPartial()
      Specified by:
      buildPartial in interface com.google.protobuf.Message.Builder
      Specified by:
      buildPartial in interface com.google.protobuf.MessageLite.Builder

    • mergeFrom

      public Form.Parameter.FillBehavior.Builder mergeFrom(com.google.protobuf.Message other)
      Specified by:
      mergeFrom in interface com.google.protobuf.Message.Builder
      Overrides:
      mergeFrom in class com.google.protobuf.AbstractMessage.Builder<Form.Parameter.FillBehavior.Builder>

    • mergeFrom

      public Form.Parameter.FillBehavior.Builder mergeFrom(Form.Parameter.FillBehavior other)

    • isInitialized

      public final boolean isInitialized()
      Specified by:
      isInitialized in interface com.google.protobuf.MessageLiteOrBuilder
      Overrides:
      isInitialized in class com.google.protobuf.GeneratedMessage.Builder<Form.Parameter.FillBehavior.Builder>

    • mergeFrom

      public Form.Parameter.FillBehavior.Builder mergeFrom(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) throws IOException
      Specified by:
      mergeFrom in interface com.google.protobuf.Message.Builder
      Specified by:
      mergeFrom in interface com.google.protobuf.MessageLite.Builder
      Overrides:
      mergeFrom in class com.google.protobuf.AbstractMessage.Builder<Form.Parameter.FillBehavior.Builder>
      Throws:
      IOException

    • hasInitialPromptFulfillment

      public 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.v3beta1.Fulfillment initial_prompt_fulfillment = 3 [(.google.api.field_behavior) = REQUIRED];
      Specified by:
      hasInitialPromptFulfillment in interface Form.Parameter.FillBehaviorOrBuilder
      Returns:
      Whether the initialPromptFulfillment field is set.

    • getInitialPromptFulfillment

      public 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.v3beta1.Fulfillment initial_prompt_fulfillment = 3 [(.google.api.field_behavior) = REQUIRED];
      Specified by:
      getInitialPromptFulfillment in interface Form.Parameter.FillBehaviorOrBuilder
      Returns:
      The initialPromptFulfillment.

    • setInitialPromptFulfillment

      public Form.Parameter.FillBehavior.Builder setInitialPromptFulfillment(Fulfillment value)
       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.v3beta1.Fulfillment initial_prompt_fulfillment = 3 [(.google.api.field_behavior) = REQUIRED];

    • setInitialPromptFulfillment

      public Form.Parameter.FillBehavior.Builder setInitialPromptFulfillment(Fulfillment.Builder builderForValue)
       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.v3beta1.Fulfillment initial_prompt_fulfillment = 3 [(.google.api.field_behavior) = REQUIRED];

    • mergeInitialPromptFulfillment

      public Form.Parameter.FillBehavior.Builder mergeInitialPromptFulfillment(Fulfillment value)
       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.v3beta1.Fulfillment initial_prompt_fulfillment = 3 [(.google.api.field_behavior) = REQUIRED];

    • clearInitialPromptFulfillment

      public Form.Parameter.FillBehavior.Builder clearInitialPromptFulfillment()
       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.v3beta1.Fulfillment initial_prompt_fulfillment = 3 [(.google.api.field_behavior) = REQUIRED];

    • getInitialPromptFulfillmentBuilder

      public Fulfillment.Builder getInitialPromptFulfillmentBuilder()
       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.v3beta1.Fulfillment initial_prompt_fulfillment = 3 [(.google.api.field_behavior) = REQUIRED];

    • getInitialPromptFulfillmentOrBuilder

      public 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.v3beta1.Fulfillment initial_prompt_fulfillment = 3 [(.google.api.field_behavior) = REQUIRED];
      Specified by:
      getInitialPromptFulfillmentOrBuilder in interface Form.Parameter.FillBehaviorOrBuilder

    • getRepromptEventHandlersList

      public 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.v3beta1.EventHandler reprompt_event_handlers = 5;
      Specified by:
      getRepromptEventHandlersList in interface Form.Parameter.FillBehaviorOrBuilder

    • getRepromptEventHandlersCount

      public 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.v3beta1.EventHandler reprompt_event_handlers = 5;
      Specified by:
      getRepromptEventHandlersCount in interface Form.Parameter.FillBehaviorOrBuilder

    • getRepromptEventHandlers

      public 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.v3beta1.EventHandler reprompt_event_handlers = 5;
      Specified by:
      getRepromptEventHandlers in interface Form.Parameter.FillBehaviorOrBuilder

    • setRepromptEventHandlers

      public Form.Parameter.FillBehavior.Builder setRepromptEventHandlers(int index, EventHandler value)
       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.v3beta1.EventHandler reprompt_event_handlers = 5;

    • setRepromptEventHandlers

      public Form.Parameter.FillBehavior.Builder setRepromptEventHandlers(int index, EventHandler.Builder builderForValue)
       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.v3beta1.EventHandler reprompt_event_handlers = 5;

    • addRepromptEventHandlers

      public Form.Parameter.FillBehavior.Builder addRepromptEventHandlers(EventHandler value)
       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.v3beta1.EventHandler reprompt_event_handlers = 5;

    • addRepromptEventHandlers

      public Form.Parameter.FillBehavior.Builder addRepromptEventHandlers(int index, EventHandler value)
       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.v3beta1.EventHandler reprompt_event_handlers = 5;

    • addRepromptEventHandlers

      public Form.Parameter.FillBehavior.Builder addRepromptEventHandlers(EventHandler.Builder builderForValue)
       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.v3beta1.EventHandler reprompt_event_handlers = 5;

    • addRepromptEventHandlers

      public Form.Parameter.FillBehavior.Builder addRepromptEventHandlers(int index, EventHandler.Builder builderForValue)
       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.v3beta1.EventHandler reprompt_event_handlers = 5;

    • addAllRepromptEventHandlers

      public Form.Parameter.FillBehavior.Builder addAllRepromptEventHandlers(Iterable<? extends EventHandler> values)
       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.v3beta1.EventHandler reprompt_event_handlers = 5;

    • clearRepromptEventHandlers

      public Form.Parameter.FillBehavior.Builder clearRepromptEventHandlers()
       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.v3beta1.EventHandler reprompt_event_handlers = 5;

    • removeRepromptEventHandlers

      public Form.Parameter.FillBehavior.Builder removeRepromptEventHandlers(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.v3beta1.EventHandler reprompt_event_handlers = 5;

    • getRepromptEventHandlersBuilder

      public EventHandler.Builder getRepromptEventHandlersBuilder(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.v3beta1.EventHandler reprompt_event_handlers = 5;

    • getRepromptEventHandlersOrBuilder

      public 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.v3beta1.EventHandler reprompt_event_handlers = 5;
      Specified by:
      getRepromptEventHandlersOrBuilder in interface Form.Parameter.FillBehaviorOrBuilder

    • getRepromptEventHandlersOrBuilderList

      public 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.v3beta1.EventHandler reprompt_event_handlers = 5;
      Specified by:
      getRepromptEventHandlersOrBuilderList in interface Form.Parameter.FillBehaviorOrBuilder

    • addRepromptEventHandlersBuilder

      public EventHandler.Builder addRepromptEventHandlersBuilder()
       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.v3beta1.EventHandler reprompt_event_handlers = 5;

    • addRepromptEventHandlersBuilder

      public EventHandler.Builder addRepromptEventHandlersBuilder(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.v3beta1.EventHandler reprompt_event_handlers = 5;

    • getRepromptEventHandlersBuilderList

      public List<EventHandler.Builder> getRepromptEventHandlersBuilderList()
       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.v3beta1.EventHandler reprompt_event_handlers = 5;