public static final class Form.Parameter.FillBehavior extends GeneratedMessageV3 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
Inherited Members
com.google.protobuf.GeneratedMessageV3.<ListT>makeMutableCopy(ListT)
com.google.protobuf.GeneratedMessageV3.<ListT>makeMutableCopy(ListT,int)
com.google.protobuf.GeneratedMessageV3.<T>emptyList(java.lang.Class<T>)
Static Fields
public static final int INITIAL_PROMPT_FULFILLMENT_FIELD_NUMBER
| Field Value |
| Type |
Description |
int |
|
public static final int REPROMPT_EVENT_HANDLERS_FIELD_NUMBER
| Field Value |
| Type |
Description |
int |
|
Static Methods
public static Form.Parameter.FillBehavior getDefaultInstance()
public static final Descriptors.Descriptor getDescriptor()
public static Form.Parameter.FillBehavior.Builder newBuilder()
public static Form.Parameter.FillBehavior.Builder newBuilder(Form.Parameter.FillBehavior prototype)
public static Form.Parameter.FillBehavior parseDelimitedFrom(InputStream input)
public static Form.Parameter.FillBehavior parseDelimitedFrom(InputStream input, ExtensionRegistryLite extensionRegistry)
public static Form.Parameter.FillBehavior parseFrom(byte[] data)
| Parameter |
| Name |
Description |
data |
byte[]
|
public static Form.Parameter.FillBehavior parseFrom(byte[] data, ExtensionRegistryLite extensionRegistry)
public static Form.Parameter.FillBehavior parseFrom(ByteString data)
public static Form.Parameter.FillBehavior parseFrom(ByteString data, ExtensionRegistryLite extensionRegistry)
public static Form.Parameter.FillBehavior parseFrom(CodedInputStream input)
public static Form.Parameter.FillBehavior parseFrom(CodedInputStream input, ExtensionRegistryLite extensionRegistry)
public static Form.Parameter.FillBehavior parseFrom(InputStream input)
public static Form.Parameter.FillBehavior parseFrom(InputStream input, ExtensionRegistryLite extensionRegistry)
public static Form.Parameter.FillBehavior parseFrom(ByteBuffer data)
public static Form.Parameter.FillBehavior parseFrom(ByteBuffer data, ExtensionRegistryLite extensionRegistry)
public static Parser<Form.Parameter.FillBehavior> parser()
Methods
public boolean equals(Object obj)
| Parameter |
| Name |
Description |
obj |
Object
|
Overrides
public Form.Parameter.FillBehavior getDefaultInstanceForType()
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.
|
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];
public Parser<Form.Parameter.FillBehavior> getParserForType()
Overrides
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 6sys.no-match-defaultsys.no-input-<N>, where N can be from 1 to 6sys.no-input-defaultsys.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
|
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 6sys.no-match-defaultsys.no-input-<N>, where N can be from 1 to 6sys.no-input-defaultsys.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 |
|
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 6sys.no-match-defaultsys.no-input-<N>, where N can be from 1 to 6sys.no-input-defaultsys.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 6sys.no-match-defaultsys.no-input-<N>, where N can be from 1 to 6sys.no-input-defaultsys.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
|
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 6sys.no-match-defaultsys.no-input-<N>, where N can be from 1 to 6sys.no-input-defaultsys.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> |
|
public int getSerializedSize()
| Returns |
| Type |
Description |
int |
|
Overrides
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.
|
| Returns |
| Type |
Description |
int |
|
Overrides
protected GeneratedMessageV3.FieldAccessorTable internalGetFieldAccessorTable()
Overrides
public final boolean isInitialized()
Overrides
public Form.Parameter.FillBehavior.Builder newBuilderForType()
protected Form.Parameter.FillBehavior.Builder newBuilderForType(GeneratedMessageV3.BuilderParent parent)
Overrides
protected Object newInstance(GeneratedMessageV3.UnusedPrivateParameter unused)
| Returns |
| Type |
Description |
Object |
|
Overrides
public Form.Parameter.FillBehavior.Builder toBuilder()
public void writeTo(CodedOutputStream output)
Overrides
