Class Form.Parameter.FillBehavior.Builder (0.19.0)

public static final class Form.Parameter.FillBehavior.Builder extends 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

Inheritance

Object > AbstractMessageLite.Builder<MessageType,BuilderType> > AbstractMessage.Builder<BuilderType> > GeneratedMessageV3.Builder > Form.Parameter.FillBehavior.Builder

Implements

Form.Parameter.FillBehaviorOrBuilder

Inherited Members

AbstractMessage.Builder.findInitializationErrors()

AbstractMessage.Builder.getInitializationErrorString()

AbstractMessage.Builder.internalMergeFrom(AbstractMessageLite)

AbstractMessage.Builder.mergeFrom(byte[])

AbstractMessage.Builder.mergeFrom(byte[],ExtensionRegistryLite)

AbstractMessage.Builder.mergeFrom(byte[],int,int)

AbstractMessage.Builder.mergeFrom(byte[],int,int,ExtensionRegistryLite)

AbstractMessage.Builder.mergeFrom(ByteString)

AbstractMessage.Builder.mergeFrom(ByteString,ExtensionRegistryLite)

AbstractMessage.Builder.mergeFrom(CodedInputStream)

AbstractMessage.Builder.mergeFrom(CodedInputStream,ExtensionRegistryLite)

AbstractMessage.Builder.mergeFrom(Message)

AbstractMessage.Builder.mergeFrom(InputStream)

AbstractMessage.Builder.mergeFrom(InputStream,ExtensionRegistryLite)

AbstractMessage.Builder.newUninitializedMessageException(Message)

AbstractMessage.Builder.toString()

AbstractMessageLite.Builder.<T>addAll(Iterable<T>,Collection<? super T>)

AbstractMessageLite.Builder.<T>addAll(Iterable<T>,List<? super T>)

AbstractMessageLite.Builder.internalMergeFrom(MessageType)

AbstractMessageLite.Builder.mergeDelimitedFrom(InputStream)

AbstractMessageLite.Builder.mergeDelimitedFrom(InputStream,ExtensionRegistryLite)

AbstractMessageLite.Builder.mergeFrom(MessageLite)

AbstractMessageLite.Builder.newUninitializedMessageException(MessageLite)

GeneratedMessageV3.Builder.addRepeatedField(Descriptors.FieldDescriptor,Object)

GeneratedMessageV3.Builder.clear()

GeneratedMessageV3.Builder.clearField(Descriptors.FieldDescriptor)

GeneratedMessageV3.Builder.clearOneof(Descriptors.OneofDescriptor)

GeneratedMessageV3.Builder.clone()

GeneratedMessageV3.Builder.getAllFields()

GeneratedMessageV3.Builder.getDescriptorForType()

GeneratedMessageV3.Builder.getField(Descriptors.FieldDescriptor)

GeneratedMessageV3.Builder.getFieldBuilder(Descriptors.FieldDescriptor)

GeneratedMessageV3.Builder.getOneofFieldDescriptor(Descriptors.OneofDescriptor)

GeneratedMessageV3.Builder.getParentForChildren()

GeneratedMessageV3.Builder.getRepeatedField(Descriptors.FieldDescriptor,int)

GeneratedMessageV3.Builder.getRepeatedFieldBuilder(Descriptors.FieldDescriptor,int)

GeneratedMessageV3.Builder.getRepeatedFieldCount(Descriptors.FieldDescriptor)

com.google.protobuf.GeneratedMessageV3.Builder.getUnknownFieldSetBuilder()

GeneratedMessageV3.Builder.getUnknownFields()

GeneratedMessageV3.Builder.hasField(Descriptors.FieldDescriptor)

GeneratedMessageV3.Builder.hasOneof(Descriptors.OneofDescriptor)

GeneratedMessageV3.Builder.internalGetFieldAccessorTable()

GeneratedMessageV3.Builder.internalGetMapField(int)

GeneratedMessageV3.Builder.internalGetMutableMapField(int)

GeneratedMessageV3.Builder.isClean()

GeneratedMessageV3.Builder.isInitialized()

GeneratedMessageV3.Builder.markClean()

GeneratedMessageV3.Builder.mergeUnknownFields(UnknownFieldSet)

com.google.protobuf.GeneratedMessageV3.Builder.mergeUnknownLengthDelimitedField(int,com.google.protobuf.ByteString)

com.google.protobuf.GeneratedMessageV3.Builder.mergeUnknownVarintField(int,int)

GeneratedMessageV3.Builder.newBuilderForField(Descriptors.FieldDescriptor)

GeneratedMessageV3.Builder.onBuilt()

GeneratedMessageV3.Builder.onChanged()

com.google.protobuf.GeneratedMessageV3.Builder.parseUnknownField(com.google.protobuf.CodedInputStream,com.google.protobuf.ExtensionRegistryLite,int)

GeneratedMessageV3.Builder.setField(Descriptors.FieldDescriptor,Object)

GeneratedMessageV3.Builder.setRepeatedField(Descriptors.FieldDescriptor,int,Object)

com.google.protobuf.GeneratedMessageV3.Builder.setUnknownFieldSetBuilder(com.google.protobuf.UnknownFieldSet.Builder)

GeneratedMessageV3.Builder.setUnknownFields(UnknownFieldSet)

GeneratedMessageV3.Builder.setUnknownFieldsProto3(UnknownFieldSet)

Object.equals(Object)

Object.finalize()

Object.getClass()

Object.hashCode()

Object.notify()

Object.notifyAll()

Object.wait()

Object.wait(long)

Object.wait(long,int)

Static Methods

getDescriptor()

public static final Descriptors.Descriptor getDescriptor()

Returns

Type	Description
Descriptor

Methods

addAllRepromptEventHandlers(Iterable<? extends EventHandler> values)

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;

Parameter

Name	Description
values	`Iterable<? extends com.google.cloud.dialogflow.cx.v3beta1.EventHandler>`

Returns

Type	Description
Form.Parameter.FillBehavior.Builder

addRepeatedField(Descriptors.FieldDescriptor field, Object value)

public Form.Parameter.FillBehavior.Builder addRepeatedField(Descriptors.FieldDescriptor field, Object value)

Parameters

Name	Description
field	`FieldDescriptor`
value	`Object`

Returns

Type	Description
Form.Parameter.FillBehavior.Builder

Overrides

GeneratedMessageV3.Builder<BuilderType>.addRepeatedField(Descriptors.FieldDescriptor field, Object value)

addRepromptEventHandlers(EventHandler value)

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;

Parameter

Name	Description
value	`EventHandler`

Returns

Type	Description
Form.Parameter.FillBehavior.Builder

addRepromptEventHandlers(EventHandler.Builder builderForValue)

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;

Parameter

Name	Description
builderForValue	`EventHandler.Builder`

Returns

Type	Description
Form.Parameter.FillBehavior.Builder

addRepromptEventHandlers(int index, EventHandler value)

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;

Parameters

Name	Description
index	`int`
value	`EventHandler`

Returns

Type	Description
Form.Parameter.FillBehavior.Builder

addRepromptEventHandlers(int index, EventHandler.Builder builderForValue)

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;

Parameters

Name	Description
index	`int`
builderForValue	`EventHandler.Builder`

Returns

Type	Description
Form.Parameter.FillBehavior.Builder

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;

Returns

Type	Description
EventHandler.Builder

addRepromptEventHandlersBuilder(int index)

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;

Parameter

Name	Description
index	`int`

Returns

Type	Description
EventHandler.Builder

build()

public Form.Parameter.FillBehavior build()

Returns

Type	Description
Form.Parameter.FillBehavior

buildPartial()

public Form.Parameter.FillBehavior buildPartial()

Returns

Type	Description
Form.Parameter.FillBehavior

clear()

public Form.Parameter.FillBehavior.Builder clear()

Returns

Type	Description
Form.Parameter.FillBehavior.Builder

Overrides

GeneratedMessageV3.Builder<BuilderType>.clear()

clearField(Descriptors.FieldDescriptor field)

public Form.Parameter.FillBehavior.Builder clearField(Descriptors.FieldDescriptor field)

Parameter

Name	Description
field	`FieldDescriptor`

Returns

Type	Description
Form.Parameter.FillBehavior.Builder

Overrides

GeneratedMessageV3.Builder<BuilderType>.clearField(Descriptors.FieldDescriptor field)

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];

Returns

Type	Description
Form.Parameter.FillBehavior.Builder

clearOneof(Descriptors.OneofDescriptor oneof)

public Form.Parameter.FillBehavior.Builder clearOneof(Descriptors.OneofDescriptor oneof)

Parameter

Name	Description
oneof	`OneofDescriptor`

Returns

Type	Description
Form.Parameter.FillBehavior.Builder

Overrides

GeneratedMessageV3.Builder<BuilderType>.clearOneof(Descriptors.OneofDescriptor oneof)

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;

Returns

Type	Description
Form.Parameter.FillBehavior.Builder

clone()

public Form.Parameter.FillBehavior.Builder clone()

Returns

Type	Description
Form.Parameter.FillBehavior.Builder

Overrides

GeneratedMessageV3.Builder<BuilderType>.clone()

getDefaultInstanceForType()

public Form.Parameter.FillBehavior getDefaultInstanceForType()

Returns

Type	Description
Form.Parameter.FillBehavior

getDescriptorForType()

public Descriptors.Descriptor getDescriptorForType()

Returns

Type	Description
Descriptor

Overrides

GeneratedMessageV3.Builder<BuilderType>.getDescriptorForType()

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];

Returns

Type	Description
Fulfillment	The initialPromptFulfillment.

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];

Returns

Type	Description
Fulfillment.Builder

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];

Returns

Type	Description
FulfillmentOrBuilder

getRepromptEventHandlers(int index)

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;

Parameter

Name	Description
index	`int`

Returns

Type	Description
EventHandler

getRepromptEventHandlersBuilder(int index)

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;

Parameter

Name	Description
index	`int`

Returns

Type	Description
EventHandler.Builder

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;

Returns

Type	Description
List<Builder>

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;

Returns

Type	Description
int

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;

Returns

Type	Description
List<EventHandler>

getRepromptEventHandlersOrBuilder(int index)

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;

Parameter

Name	Description
index	`int`

Returns

Type	Description
EventHandlerOrBuilder

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;

Returns

Type	Description
List<? extends com.google.cloud.dialogflow.cx.v3beta1.EventHandlerOrBuilder>

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];

Returns

Type	Description
boolean	Whether the initialPromptFulfillment field is set.

internalGetFieldAccessorTable()

protected GeneratedMessageV3.FieldAccessorTable internalGetFieldAccessorTable()

Returns

Type	Description
FieldAccessorTable

Overrides

GeneratedMessageV3.Builder<BuilderType>.internalGetFieldAccessorTable()

isInitialized()

public final boolean isInitialized()

Returns

Type	Description
boolean

Overrides

GeneratedMessageV3.Builder<BuilderType>.isInitialized()

mergeFrom(Form.Parameter.FillBehavior other)

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

Parameter

Name	Description
other	`Form.Parameter.FillBehavior`

Returns

Type	Description
Form.Parameter.FillBehavior.Builder

mergeFrom(CodedInputStream input, ExtensionRegistryLite extensionRegistry)

public Form.Parameter.FillBehavior.Builder mergeFrom(CodedInputStream input, ExtensionRegistryLite extensionRegistry)

Parameters

Name	Description
input	`CodedInputStream`
extensionRegistry	`ExtensionRegistryLite`

Returns

Type	Description
Form.Parameter.FillBehavior.Builder

Overrides

AbstractMessage.Builder<BuilderType>.mergeFrom(CodedInputStream input, ExtensionRegistryLite extensionRegistry)

Exceptions

Type	Description
IOException

mergeFrom(Message other)

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

Parameter

Name	Description
other	`Message`

Returns

Type	Description
Form.Parameter.FillBehavior.Builder

Overrides

AbstractMessage.Builder<BuilderType>.mergeFrom(Message other)

mergeInitialPromptFulfillment(Fulfillment value)

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];

Parameter

Name	Description
value	`Fulfillment`

Returns

Type	Description
Form.Parameter.FillBehavior.Builder

mergeUnknownFields(UnknownFieldSet unknownFields)

public final Form.Parameter.FillBehavior.Builder mergeUnknownFields(UnknownFieldSet unknownFields)

Parameter

Name	Description
unknownFields	`UnknownFieldSet`

Returns

Type	Description
Form.Parameter.FillBehavior.Builder

Overrides

GeneratedMessageV3.Builder<BuilderType>.mergeUnknownFields(UnknownFieldSet unknownFields)

removeRepromptEventHandlers(int index)

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;

Parameter

Name	Description
index	`int`

Returns

Type	Description
Form.Parameter.FillBehavior.Builder

setField(Descriptors.FieldDescriptor field, Object value)

public Form.Parameter.FillBehavior.Builder setField(Descriptors.FieldDescriptor field, Object value)

Parameters

Name	Description
field	`FieldDescriptor`
value	`Object`

Returns

Type	Description
Form.Parameter.FillBehavior.Builder

Overrides

GeneratedMessageV3.Builder<BuilderType>.setField(Descriptors.FieldDescriptor field, Object value)

setInitialPromptFulfillment(Fulfillment value)

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];

Parameter

Name	Description
value	`Fulfillment`

Returns

Type	Description
Form.Parameter.FillBehavior.Builder

setInitialPromptFulfillment(Fulfillment.Builder builderForValue)

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];

Parameter

Name	Description
builderForValue	`Fulfillment.Builder`

Returns

Type	Description
Form.Parameter.FillBehavior.Builder

setRepeatedField(Descriptors.FieldDescriptor field, int index, Object value)

public Form.Parameter.FillBehavior.Builder setRepeatedField(Descriptors.FieldDescriptor field, int index, Object value)

Parameters

Name	Description
field	`FieldDescriptor`
index	`int`
value	`Object`

Returns

Type	Description
Form.Parameter.FillBehavior.Builder

Overrides

GeneratedMessageV3.Builder<BuilderType>.setRepeatedField(Descriptors.FieldDescriptor field, int index, Object value)

setRepromptEventHandlers(int index, EventHandler value)

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;

Parameters

Name	Description
index	`int`
value	`EventHandler`

Returns

Type	Description
Form.Parameter.FillBehavior.Builder

setRepromptEventHandlers(int index, EventHandler.Builder builderForValue)

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;

Parameters

Name	Description
index	`int`
builderForValue	`EventHandler.Builder`

Returns

Type	Description
Form.Parameter.FillBehavior.Builder

setUnknownFields(UnknownFieldSet unknownFields)

public final Form.Parameter.FillBehavior.Builder setUnknownFields(UnknownFieldSet unknownFields)

Parameter

Name	Description
unknownFields	`UnknownFieldSet`

Returns

Type	Description
Form.Parameter.FillBehavior.Builder

Overrides

GeneratedMessageV3.Builder<BuilderType>.setUnknownFields(UnknownFieldSet unknownFields)