public static final class Form.Parameter.FillBehavior.Builder extends com.google.protobuf.GeneratedMessageV3.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| Modifier and Type | Method and Description |
|---|---|
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.
|
Form.Parameter.FillBehavior.Builder |
addRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field,
Object value) |
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.
|
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.
|
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.
|
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.
|
EventHandler.Builder |
addRepromptEventHandlersBuilder()
The handlers for parameter-level events, used to provide reprompt for
the parameter or transition to a different page/flow.
|
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.
|
Form.Parameter.FillBehavior |
build() |
Form.Parameter.FillBehavior |
buildPartial() |
Form.Parameter.FillBehavior.Builder |
clear() |
Form.Parameter.FillBehavior.Builder |
clearField(com.google.protobuf.Descriptors.FieldDescriptor field) |
Form.Parameter.FillBehavior.Builder |
clearInitialPromptFulfillment()
Required.
|
Form.Parameter.FillBehavior.Builder |
clearOneof(com.google.protobuf.Descriptors.OneofDescriptor oneof) |
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.
|
Form.Parameter.FillBehavior.Builder |
clone() |
Form.Parameter.FillBehavior |
getDefaultInstanceForType() |
static com.google.protobuf.Descriptors.Descriptor |
getDescriptor() |
com.google.protobuf.Descriptors.Descriptor |
getDescriptorForType() |
Fulfillment |
getInitialPromptFulfillment()
Required.
|
Fulfillment.Builder |
getInitialPromptFulfillmentBuilder()
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.
|
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.
|
List<EventHandler.Builder> |
getRepromptEventHandlersBuilderList()
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.
|
protected com.google.protobuf.GeneratedMessageV3.FieldAccessorTable |
internalGetFieldAccessorTable() |
boolean |
isInitialized() |
Form.Parameter.FillBehavior.Builder |
mergeFrom(com.google.protobuf.CodedInputStream input,
com.google.protobuf.ExtensionRegistryLite extensionRegistry) |
Form.Parameter.FillBehavior.Builder |
mergeFrom(Form.Parameter.FillBehavior other) |
Form.Parameter.FillBehavior.Builder |
mergeFrom(com.google.protobuf.Message other) |
Form.Parameter.FillBehavior.Builder |
mergeInitialPromptFulfillment(Fulfillment value)
Required.
|
Form.Parameter.FillBehavior.Builder |
mergeUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields) |
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.
|
Form.Parameter.FillBehavior.Builder |
setField(com.google.protobuf.Descriptors.FieldDescriptor field,
Object value) |
Form.Parameter.FillBehavior.Builder |
setInitialPromptFulfillment(Fulfillment.Builder builderForValue)
Required.
|
Form.Parameter.FillBehavior.Builder |
setInitialPromptFulfillment(Fulfillment value)
Required.
|
Form.Parameter.FillBehavior.Builder |
setRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field,
int index,
Object value) |
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.
|
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.
|
Form.Parameter.FillBehavior.Builder |
setUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields) |
getAllFields, getField, getFieldBuilder, getOneofFieldDescriptor, getParentForChildren, getRepeatedField, getRepeatedFieldBuilder, getRepeatedFieldCount, getUnknownFields, getUnknownFieldSetBuilder, hasField, hasOneof, internalGetMapField, internalGetMapFieldReflection, internalGetMutableMapField, internalGetMutableMapFieldReflection, isClean, markClean, mergeUnknownLengthDelimitedField, mergeUnknownVarintField, newBuilderForField, onBuilt, onChanged, parseUnknownField, setUnknownFieldSetBuilder, setUnknownFieldsProto3findInitializationErrors, getInitializationErrorString, internalMergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, newUninitializedMessageException, toStringaddAll, addAll, mergeDelimitedFrom, mergeDelimitedFrom, newUninitializedMessageExceptionequals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, waitpublic static final com.google.protobuf.Descriptors.Descriptor getDescriptor()
protected com.google.protobuf.GeneratedMessageV3.FieldAccessorTable internalGetFieldAccessorTable()
internalGetFieldAccessorTable in class com.google.protobuf.GeneratedMessageV3.Builder<Form.Parameter.FillBehavior.Builder>public Form.Parameter.FillBehavior.Builder clear()
clear in interface com.google.protobuf.Message.Builderclear in interface com.google.protobuf.MessageLite.Builderclear in class com.google.protobuf.GeneratedMessageV3.Builder<Form.Parameter.FillBehavior.Builder>public com.google.protobuf.Descriptors.Descriptor getDescriptorForType()
getDescriptorForType in interface com.google.protobuf.Message.BuildergetDescriptorForType in interface com.google.protobuf.MessageOrBuildergetDescriptorForType in class com.google.protobuf.GeneratedMessageV3.Builder<Form.Parameter.FillBehavior.Builder>public Form.Parameter.FillBehavior getDefaultInstanceForType()
getDefaultInstanceForType in interface com.google.protobuf.MessageLiteOrBuildergetDefaultInstanceForType in interface com.google.protobuf.MessageOrBuilderpublic Form.Parameter.FillBehavior build()
build in interface com.google.protobuf.Message.Builderbuild in interface com.google.protobuf.MessageLite.Builderpublic Form.Parameter.FillBehavior buildPartial()
buildPartial in interface com.google.protobuf.Message.BuilderbuildPartial in interface com.google.protobuf.MessageLite.Builderpublic Form.Parameter.FillBehavior.Builder clone()
clone in interface com.google.protobuf.Message.Builderclone in interface com.google.protobuf.MessageLite.Builderclone in class com.google.protobuf.GeneratedMessageV3.Builder<Form.Parameter.FillBehavior.Builder>public Form.Parameter.FillBehavior.Builder setField(com.google.protobuf.Descriptors.FieldDescriptor field, Object value)
setField in interface com.google.protobuf.Message.BuildersetField in class com.google.protobuf.GeneratedMessageV3.Builder<Form.Parameter.FillBehavior.Builder>public Form.Parameter.FillBehavior.Builder clearField(com.google.protobuf.Descriptors.FieldDescriptor field)
clearField in interface com.google.protobuf.Message.BuilderclearField in class com.google.protobuf.GeneratedMessageV3.Builder<Form.Parameter.FillBehavior.Builder>public Form.Parameter.FillBehavior.Builder clearOneof(com.google.protobuf.Descriptors.OneofDescriptor oneof)
clearOneof in interface com.google.protobuf.Message.BuilderclearOneof in class com.google.protobuf.GeneratedMessageV3.Builder<Form.Parameter.FillBehavior.Builder>public Form.Parameter.FillBehavior.Builder setRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, int index, Object value)
setRepeatedField in interface com.google.protobuf.Message.BuildersetRepeatedField in class com.google.protobuf.GeneratedMessageV3.Builder<Form.Parameter.FillBehavior.Builder>public Form.Parameter.FillBehavior.Builder addRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, Object value)
addRepeatedField in interface com.google.protobuf.Message.BuilderaddRepeatedField in class com.google.protobuf.GeneratedMessageV3.Builder<Form.Parameter.FillBehavior.Builder>public Form.Parameter.FillBehavior.Builder mergeFrom(com.google.protobuf.Message other)
mergeFrom in interface com.google.protobuf.Message.BuildermergeFrom in class com.google.protobuf.AbstractMessage.Builder<Form.Parameter.FillBehavior.Builder>public Form.Parameter.FillBehavior.Builder mergeFrom(Form.Parameter.FillBehavior other)
public final boolean isInitialized()
isInitialized in interface com.google.protobuf.MessageLiteOrBuilderisInitialized in class com.google.protobuf.GeneratedMessageV3.Builder<Form.Parameter.FillBehavior.Builder>public Form.Parameter.FillBehavior.Builder mergeFrom(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) throws IOException
mergeFrom in interface com.google.protobuf.Message.BuildermergeFrom in interface com.google.protobuf.MessageLite.BuildermergeFrom in class com.google.protobuf.AbstractMessage.Builder<Form.Parameter.FillBehavior.Builder>IOExceptionpublic 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];
hasInitialPromptFulfillment in interface Form.Parameter.FillBehaviorOrBuilderpublic 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];
getInitialPromptFulfillment in interface Form.Parameter.FillBehaviorOrBuilderpublic 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];
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];
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];
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];
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];
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];
getInitialPromptFulfillmentOrBuilder in interface Form.Parameter.FillBehaviorOrBuilderpublic 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;
getRepromptEventHandlersList in interface Form.Parameter.FillBehaviorOrBuilderpublic 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;
getRepromptEventHandlersCount in interface Form.Parameter.FillBehaviorOrBuilderpublic 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;
getRepromptEventHandlers in interface Form.Parameter.FillBehaviorOrBuilderpublic 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;
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;
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;
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;
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;
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;
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;
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;
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;
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;
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;
getRepromptEventHandlersOrBuilder in interface Form.Parameter.FillBehaviorOrBuilderpublic 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;
getRepromptEventHandlersOrBuilderList in interface Form.Parameter.FillBehaviorOrBuilderpublic 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;
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;
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;
public final Form.Parameter.FillBehavior.Builder setUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields)
setUnknownFields in interface com.google.protobuf.Message.BuildersetUnknownFields in class com.google.protobuf.GeneratedMessageV3.Builder<Form.Parameter.FillBehavior.Builder>public final Form.Parameter.FillBehavior.Builder mergeUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields)
mergeUnknownFields in interface com.google.protobuf.Message.BuildermergeUnknownFields in class com.google.protobuf.GeneratedMessageV3.Builder<Form.Parameter.FillBehavior.Builder>Copyright © 2025 Google LLC. All rights reserved.