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.v3.Form.Parameter.FillBehavior
Inherited Members
com.google.protobuf.GeneratedMessageV3.Builder.getUnknownFieldSetBuilder()
com.google.protobuf.GeneratedMessageV3.Builder.mergeUnknownLengthDelimitedField(int,com.google.protobuf.ByteString)
com.google.protobuf.GeneratedMessageV3.Builder.mergeUnknownVarintField(int,int)
com.google.protobuf.GeneratedMessageV3.Builder.parseUnknownField(com.google.protobuf.CodedInputStream,com.google.protobuf.ExtensionRegistryLite,int)
com.google.protobuf.GeneratedMessageV3.Builder.setUnknownFieldSetBuilder(com.google.protobuf.UnknownFieldSet.Builder)
Static Methods
public static final Descriptors.Descriptor getDescriptor()
Returns
Methods
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.v3.EventHandler reprompt_event_handlers = 5;
Parameter
Name |
Description |
values |
Iterable<? extends com.google.cloud.dialogflow.cx.v3.EventHandler>
|
Returns
public Form.Parameter.FillBehavior.Builder addRepeatedField(Descriptors.FieldDescriptor field, Object value)
Parameters
Returns
Overrides
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.v3.EventHandler reprompt_event_handlers = 5;
Parameter
Returns
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.v3.EventHandler reprompt_event_handlers = 5;
Parameter
Returns
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.v3.EventHandler reprompt_event_handlers = 5;
Parameters
Returns
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.v3.EventHandler reprompt_event_handlers = 5;
Parameters
Returns
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.v3.EventHandler reprompt_event_handlers = 5;
Returns
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.v3.EventHandler reprompt_event_handlers = 5;
Parameter
Name |
Description |
index |
int
|
Returns
public Form.Parameter.FillBehavior build()
Returns
public Form.Parameter.FillBehavior buildPartial()
Returns
public Form.Parameter.FillBehavior.Builder clear()
Returns
Overrides
public Form.Parameter.FillBehavior.Builder clearField(Descriptors.FieldDescriptor field)
Parameter
Returns
Overrides
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.v3.Fulfillment initial_prompt_fulfillment = 3 [(.google.api.field_behavior) = REQUIRED];
Returns
public Form.Parameter.FillBehavior.Builder clearOneof(Descriptors.OneofDescriptor oneof)
Parameter
Returns
Overrides
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.v3.EventHandler reprompt_event_handlers = 5;
Returns
public Form.Parameter.FillBehavior.Builder clone()
Returns
Overrides
public Form.Parameter.FillBehavior getDefaultInstanceForType()
Returns
public Descriptors.Descriptor getDescriptorForType()
Returns
Overrides
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.v3.Fulfillment initial_prompt_fulfillment = 3 [(.google.api.field_behavior) = REQUIRED];
Returns
Type |
Description |
Fulfillment |
The initialPromptFulfillment.
|
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.v3.Fulfillment initial_prompt_fulfillment = 3 [(.google.api.field_behavior) = REQUIRED];
Returns
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.v3.Fulfillment initial_prompt_fulfillment = 3 [(.google.api.field_behavior) = REQUIRED];
Returns
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.v3.EventHandler reprompt_event_handlers = 5;
Parameter
Name |
Description |
index |
int
|
Returns
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.v3.EventHandler reprompt_event_handlers = 5;
Parameter
Name |
Description |
index |
int
|
Returns
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.v3.EventHandler reprompt_event_handlers = 5;
Returns
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.v3.EventHandler reprompt_event_handlers = 5;
Returns
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.v3.EventHandler reprompt_event_handlers = 5;
Returns
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.v3.EventHandler reprompt_event_handlers = 5;
Parameter
Name |
Description |
index |
int
|
Returns
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.v3.EventHandler reprompt_event_handlers = 5;
Returns
Type |
Description |
List<? extends com.google.cloud.dialogflow.cx.v3.EventHandlerOrBuilder> |
|
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.v3.Fulfillment initial_prompt_fulfillment = 3 [(.google.api.field_behavior) = REQUIRED];
Returns
Type |
Description |
boolean |
Whether the initialPromptFulfillment field is set.
|
protected GeneratedMessageV3.FieldAccessorTable internalGetFieldAccessorTable()
Returns
Overrides
public final boolean isInitialized()
Returns
Overrides
public Form.Parameter.FillBehavior.Builder mergeFrom(Form.Parameter.FillBehavior other)
Parameter
Returns
public Form.Parameter.FillBehavior.Builder mergeFrom(CodedInputStream input, ExtensionRegistryLite extensionRegistry)
Parameters
Returns
Overrides
Exceptions
public Form.Parameter.FillBehavior.Builder mergeFrom(Message other)
Parameter
Returns
Overrides
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.v3.Fulfillment initial_prompt_fulfillment = 3 [(.google.api.field_behavior) = REQUIRED];
Parameter
Returns
public final Form.Parameter.FillBehavior.Builder mergeUnknownFields(UnknownFieldSet unknownFields)
Parameter
Returns
Overrides
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.v3.EventHandler reprompt_event_handlers = 5;
Parameter
Name |
Description |
index |
int
|
Returns
public Form.Parameter.FillBehavior.Builder setField(Descriptors.FieldDescriptor field, Object value)
Parameters
Returns
Overrides
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.v3.Fulfillment initial_prompt_fulfillment = 3 [(.google.api.field_behavior) = REQUIRED];
Parameter
Returns
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.v3.Fulfillment initial_prompt_fulfillment = 3 [(.google.api.field_behavior) = REQUIRED];
Parameter
Returns
public Form.Parameter.FillBehavior.Builder setRepeatedField(Descriptors.FieldDescriptor field, int index, Object value)
Parameters
Returns
Overrides
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.v3.EventHandler reprompt_event_handlers = 5;
Parameters
Returns
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.v3.EventHandler reprompt_event_handlers = 5;
Parameters
Returns
public final Form.Parameter.FillBehavior.Builder setUnknownFields(UnknownFieldSet unknownFields)
Parameter
Returns
Overrides