public class PostTextResult extends Object implements Serializable
Constructor and Description |
---|
PostTextResult() |
Modifier and Type | Method and Description |
---|---|
PostTextResult |
addsessionAttributesEntry(String key,
String value)
A map of key-value pairs representing the session-specific context
information.
|
PostTextResult |
addslotsEntry(String key,
String value)
The intent slots (name/value pairs) that Amazon Lex detected so far from
the user input in the conversation.
|
PostTextResult |
clearsessionAttributesEntries()
Removes all the entries added into sessionAttributes.
|
PostTextResult |
clearslotsEntries()
Removes all the entries added into slots.
|
boolean |
equals(Object obj) |
String |
getDialogState()
Identifies the current state of the user interaction.
|
String |
getIntentName()
The current user intent that Amazon Lex is aware of.
|
String |
getMessage()
A message to convey to the user.
|
ResponseCard |
getResponseCard()
Represents the options that the user has to respond to the current
prompt.
|
Map<String,String> |
getSessionAttributes()
A map of key-value pairs representing the session-specific context
information.
|
Map<String,String> |
getSlots()
The intent slots (name/value pairs) that Amazon Lex detected so far from
the user input in the conversation.
|
String |
getSlotToElicit()
If the
dialogState value is ElicitSlot , returns
the name of the slot for which Amazon Lex is eliciting a value. |
int |
hashCode() |
void |
setDialogState(DialogState dialogState)
Identifies the current state of the user interaction.
|
void |
setDialogState(String dialogState)
Identifies the current state of the user interaction.
|
void |
setIntentName(String intentName)
The current user intent that Amazon Lex is aware of.
|
void |
setMessage(String message)
A message to convey to the user.
|
void |
setResponseCard(ResponseCard responseCard)
Represents the options that the user has to respond to the current
prompt.
|
void |
setSessionAttributes(Map<String,String> sessionAttributes)
A map of key-value pairs representing the session-specific context
information.
|
void |
setSlots(Map<String,String> slots)
The intent slots (name/value pairs) that Amazon Lex detected so far from
the user input in the conversation.
|
void |
setSlotToElicit(String slotToElicit)
If the
dialogState value is ElicitSlot , returns
the name of the slot for which Amazon Lex is eliciting a value. |
String |
toString()
Returns a string representation of this object; useful for testing and
debugging.
|
PostTextResult |
withDialogState(DialogState dialogState)
Identifies the current state of the user interaction.
|
PostTextResult |
withDialogState(String dialogState)
Identifies the current state of the user interaction.
|
PostTextResult |
withIntentName(String intentName)
The current user intent that Amazon Lex is aware of.
|
PostTextResult |
withMessage(String message)
A message to convey to the user.
|
PostTextResult |
withResponseCard(ResponseCard responseCard)
Represents the options that the user has to respond to the current
prompt.
|
PostTextResult |
withSessionAttributes(Map<String,String> sessionAttributes)
A map of key-value pairs representing the session-specific context
information.
|
PostTextResult |
withSlots(Map<String,String> slots)
The intent slots (name/value pairs) that Amazon Lex detected so far from
the user input in the conversation.
|
PostTextResult |
withSlotToElicit(String slotToElicit)
If the
dialogState value is ElicitSlot , returns
the name of the slot for which Amazon Lex is eliciting a value. |
public String getIntentName()
The current user intent that Amazon Lex is aware of.
The current user intent that Amazon Lex is aware of.
public void setIntentName(String intentName)
The current user intent that Amazon Lex is aware of.
intentName
- The current user intent that Amazon Lex is aware of.
public PostTextResult withIntentName(String intentName)
The current user intent that Amazon Lex is aware of.
Returns a reference to this object so that method calls can be chained together.
intentName
- The current user intent that Amazon Lex is aware of.
public Map<String,String> getSlots()
The intent slots (name/value pairs) that Amazon Lex detected so far from the user input in the conversation.
The intent slots (name/value pairs) that Amazon Lex detected so far from the user input in the conversation.
public void setSlots(Map<String,String> slots)
The intent slots (name/value pairs) that Amazon Lex detected so far from the user input in the conversation.
slots
- The intent slots (name/value pairs) that Amazon Lex detected so far from the user input in the conversation.
public PostTextResult withSlots(Map<String,String> slots)
The intent slots (name/value pairs) that Amazon Lex detected so far from the user input in the conversation.
Returns a reference to this object so that method calls can be chained together.
slots
- The intent slots (name/value pairs) that Amazon Lex detected so far from the user input in the conversation.
public PostTextResult addslotsEntry(String key, String value)
The intent slots (name/value pairs) that Amazon Lex detected so far from the user input in the conversation.
The method adds a new key-value pair into slots parameter, and returns a reference to this object so that method calls can be chained together.
key
- The key of the entry to be added into slots.value
- The corresponding value of the entry to be added into slots.public PostTextResult clearslotsEntries()
Returns a reference to this object so that method calls can be chained together.
public Map<String,String> getSessionAttributes()
A map of key-value pairs representing the session-specific context information.
A map of key-value pairs representing the session-specific context information.
public void setSessionAttributes(Map<String,String> sessionAttributes)
A map of key-value pairs representing the session-specific context information.
sessionAttributes
- A map of key-value pairs representing the session-specific context information.
public PostTextResult withSessionAttributes(Map<String,String> sessionAttributes)
A map of key-value pairs representing the session-specific context information.
Returns a reference to this object so that method calls can be chained together.
sessionAttributes
- A map of key-value pairs representing the session-specific context information.
public PostTextResult addsessionAttributesEntry(String key, String value)
A map of key-value pairs representing the session-specific context information.
The method adds a new key-value pair into sessionAttributes parameter, and returns a reference to this object so that method calls can be chained together.
key
- The key of the entry to be added into sessionAttributes.value
- The corresponding value of the entry to be added into
sessionAttributes.public PostTextResult clearsessionAttributesEntries()
Returns a reference to this object so that method calls can be chained together.
public String getMessage()
A message to convey to the user. It can come from the bot's configuration
or a code hook (Lambda function). If the current intent is not configured
with a code hook or the code hook returned Delegate
as the
dialogAction.type
in its response, then Amazon Lex decides
the next course of action and selects an appropriate message from the bot
configuration based on the current user interaction context. For example,
if Amazon Lex is not able to understand the user input, it uses a
clarification prompt message (for more information, see the Error
Handling section in the Amazon Lex console). Another example: if the
intent requires confirmation before fulfillment, then Amazon Lex uses the
confirmation prompt message in the intent configuration. If the code hook
returns a message, Amazon Lex passes it as-is in its response to the
client.
Constraints:
Length: 1 - 1024
A message to convey to the user. It can come from the bot's
configuration or a code hook (Lambda function). If the current
intent is not configured with a code hook or the code hook
returned Delegate
as the
dialogAction.type
in its response, then Amazon Lex
decides the next course of action and selects an appropriate
message from the bot configuration based on the current user
interaction context. For example, if Amazon Lex is not able to
understand the user input, it uses a clarification prompt message
(for more information, see the Error Handling section in the
Amazon Lex console). Another example: if the intent requires
confirmation before fulfillment, then Amazon Lex uses the
confirmation prompt message in the intent configuration. If the
code hook returns a message, Amazon Lex passes it as-is in its
response to the client.
public void setMessage(String message)
A message to convey to the user. It can come from the bot's configuration
or a code hook (Lambda function). If the current intent is not configured
with a code hook or the code hook returned Delegate
as the
dialogAction.type
in its response, then Amazon Lex decides
the next course of action and selects an appropriate message from the bot
configuration based on the current user interaction context. For example,
if Amazon Lex is not able to understand the user input, it uses a
clarification prompt message (for more information, see the Error
Handling section in the Amazon Lex console). Another example: if the
intent requires confirmation before fulfillment, then Amazon Lex uses the
confirmation prompt message in the intent configuration. If the code hook
returns a message, Amazon Lex passes it as-is in its response to the
client.
Constraints:
Length: 1 - 1024
message
-
A message to convey to the user. It can come from the bot's
configuration or a code hook (Lambda function). If the current
intent is not configured with a code hook or the code hook
returned Delegate
as the
dialogAction.type
in its response, then Amazon
Lex decides the next course of action and selects an
appropriate message from the bot configuration based on the
current user interaction context. For example, if Amazon Lex
is not able to understand the user input, it uses a
clarification prompt message (for more information, see the
Error Handling section in the Amazon Lex console). Another
example: if the intent requires confirmation before
fulfillment, then Amazon Lex uses the confirmation prompt
message in the intent configuration. If the code hook returns
a message, Amazon Lex passes it as-is in its response to the
client.
public PostTextResult withMessage(String message)
A message to convey to the user. It can come from the bot's configuration
or a code hook (Lambda function). If the current intent is not configured
with a code hook or the code hook returned Delegate
as the
dialogAction.type
in its response, then Amazon Lex decides
the next course of action and selects an appropriate message from the bot
configuration based on the current user interaction context. For example,
if Amazon Lex is not able to understand the user input, it uses a
clarification prompt message (for more information, see the Error
Handling section in the Amazon Lex console). Another example: if the
intent requires confirmation before fulfillment, then Amazon Lex uses the
confirmation prompt message in the intent configuration. If the code hook
returns a message, Amazon Lex passes it as-is in its response to the
client.
Returns a reference to this object so that method calls can be chained together.
Constraints:
Length: 1 - 1024
message
-
A message to convey to the user. It can come from the bot's
configuration or a code hook (Lambda function). If the current
intent is not configured with a code hook or the code hook
returned Delegate
as the
dialogAction.type
in its response, then Amazon
Lex decides the next course of action and selects an
appropriate message from the bot configuration based on the
current user interaction context. For example, if Amazon Lex
is not able to understand the user input, it uses a
clarification prompt message (for more information, see the
Error Handling section in the Amazon Lex console). Another
example: if the intent requires confirmation before
fulfillment, then Amazon Lex uses the confirmation prompt
message in the intent configuration. If the code hook returns
a message, Amazon Lex passes it as-is in its response to the
client.
public String getDialogState()
Identifies the current state of the user interaction. Amazon Lex returns
one of the following values as dialogState
. The client can
optionally use this information to customize the user interface.
ElicitIntent
– Amazon Lex wants to elicit user intent.
For example, a user might utter an intent ("I want to order a pizza"). If Amazon Lex cannot infer the user intent from this utterance, it will return this dialogState.
ConfirmIntent
– Amazon Lex is expecting a "yes" or "no"
response.
For example, Amazon Lex wants user confirmation before fulfilling an intent.
Instead of a simple "yes" or "no," a user might respond with additional information. For example, "yes, but make it thick crust pizza" or "no, I want to order a drink". Amazon Lex can process such additional information (in these examples, update the crust type slot value, or change intent from OrderPizza to OrderDrink).
ElicitSlot
– Amazon Lex is expecting a slot value for the
current intent.
For example, suppose that in the response Amazon Lex sends this message: "What size pizza would you like?". A user might reply with the slot value (e.g., "medium"). The user might also provide additional information in the response (e.g., "medium thick crust pizza"). Amazon Lex can process such additional information appropriately.
Fulfilled
– Conveys that the Lambda function configured for
the intent has successfully fulfilled the intent.
ReadyForFulfillment
– Conveys that the client has to fulfill
the intent.
Failed
– Conveys that the conversation with the user failed.
This can happen for various reasons including that the user did not provide an appropriate response to prompts from the service (you can configure how many times Amazon Lex can prompt a user for specific information), or the Lambda function failed to fulfill the intent.
Constraints:
Allowed Values: ElicitIntent, ConfirmIntent, ElicitSlot,
Fulfilled, ReadyForFulfillment, Failed
Identifies the current state of the user interaction. Amazon Lex
returns one of the following values as dialogState
.
The client can optionally use this information to customize the
user interface.
ElicitIntent
– Amazon Lex wants to elicit user
intent.
For example, a user might utter an intent ("I want to order a pizza"). If Amazon Lex cannot infer the user intent from this utterance, it will return this dialogState.
ConfirmIntent
– Amazon Lex is expecting a "yes" or
"no" response.
For example, Amazon Lex wants user confirmation before fulfilling an intent.
Instead of a simple "yes" or "no," a user might respond with additional information. For example, "yes, but make it thick crust pizza" or "no, I want to order a drink". Amazon Lex can process such additional information (in these examples, update the crust type slot value, or change intent from OrderPizza to OrderDrink).
ElicitSlot
– Amazon Lex is expecting a slot value
for the current intent.
For example, suppose that in the response Amazon Lex sends this message: "What size pizza would you like?". A user might reply with the slot value (e.g., "medium"). The user might also provide additional information in the response (e.g., "medium thick crust pizza"). Amazon Lex can process such additional information appropriately.
Fulfilled
– Conveys that the Lambda function
configured for the intent has successfully fulfilled the intent.
ReadyForFulfillment
– Conveys that the client has to
fulfill the intent.
Failed
– Conveys that the conversation with the user
failed.
This can happen for various reasons including that the user did not provide an appropriate response to prompts from the service (you can configure how many times Amazon Lex can prompt a user for specific information), or the Lambda function failed to fulfill the intent.
DialogState
public void setDialogState(String dialogState)
Identifies the current state of the user interaction. Amazon Lex returns
one of the following values as dialogState
. The client can
optionally use this information to customize the user interface.
ElicitIntent
– Amazon Lex wants to elicit user intent.
For example, a user might utter an intent ("I want to order a pizza"). If Amazon Lex cannot infer the user intent from this utterance, it will return this dialogState.
ConfirmIntent
– Amazon Lex is expecting a "yes" or "no"
response.
For example, Amazon Lex wants user confirmation before fulfilling an intent.
Instead of a simple "yes" or "no," a user might respond with additional information. For example, "yes, but make it thick crust pizza" or "no, I want to order a drink". Amazon Lex can process such additional information (in these examples, update the crust type slot value, or change intent from OrderPizza to OrderDrink).
ElicitSlot
– Amazon Lex is expecting a slot value for the
current intent.
For example, suppose that in the response Amazon Lex sends this message: "What size pizza would you like?". A user might reply with the slot value (e.g., "medium"). The user might also provide additional information in the response (e.g., "medium thick crust pizza"). Amazon Lex can process such additional information appropriately.
Fulfilled
– Conveys that the Lambda function configured for
the intent has successfully fulfilled the intent.
ReadyForFulfillment
– Conveys that the client has to fulfill
the intent.
Failed
– Conveys that the conversation with the user failed.
This can happen for various reasons including that the user did not provide an appropriate response to prompts from the service (you can configure how many times Amazon Lex can prompt a user for specific information), or the Lambda function failed to fulfill the intent.
Constraints:
Allowed Values: ElicitIntent, ConfirmIntent, ElicitSlot,
Fulfilled, ReadyForFulfillment, Failed
dialogState
-
Identifies the current state of the user interaction. Amazon
Lex returns one of the following values as
dialogState
. The client can optionally use this
information to customize the user interface.
ElicitIntent
– Amazon Lex wants to elicit user
intent.
For example, a user might utter an intent ("I want to order a pizza"). If Amazon Lex cannot infer the user intent from this utterance, it will return this dialogState.
ConfirmIntent
– Amazon Lex is expecting a "yes"
or "no" response.
For example, Amazon Lex wants user confirmation before fulfilling an intent.
Instead of a simple "yes" or "no," a user might respond with additional information. For example, "yes, but make it thick crust pizza" or "no, I want to order a drink". Amazon Lex can process such additional information (in these examples, update the crust type slot value, or change intent from OrderPizza to OrderDrink).
ElicitSlot
– Amazon Lex is expecting a slot value
for the current intent.
For example, suppose that in the response Amazon Lex sends this message: "What size pizza would you like?". A user might reply with the slot value (e.g., "medium"). The user might also provide additional information in the response (e.g., "medium thick crust pizza"). Amazon Lex can process such additional information appropriately.
Fulfilled
– Conveys that the Lambda function
configured for the intent has successfully fulfilled the
intent.
ReadyForFulfillment
– Conveys that the client has
to fulfill the intent.
Failed
– Conveys that the conversation with the
user failed.
This can happen for various reasons including that the user did not provide an appropriate response to prompts from the service (you can configure how many times Amazon Lex can prompt a user for specific information), or the Lambda function failed to fulfill the intent.
DialogState
public PostTextResult withDialogState(String dialogState)
Identifies the current state of the user interaction. Amazon Lex returns
one of the following values as dialogState
. The client can
optionally use this information to customize the user interface.
ElicitIntent
– Amazon Lex wants to elicit user intent.
For example, a user might utter an intent ("I want to order a pizza"). If Amazon Lex cannot infer the user intent from this utterance, it will return this dialogState.
ConfirmIntent
– Amazon Lex is expecting a "yes" or "no"
response.
For example, Amazon Lex wants user confirmation before fulfilling an intent.
Instead of a simple "yes" or "no," a user might respond with additional information. For example, "yes, but make it thick crust pizza" or "no, I want to order a drink". Amazon Lex can process such additional information (in these examples, update the crust type slot value, or change intent from OrderPizza to OrderDrink).
ElicitSlot
– Amazon Lex is expecting a slot value for the
current intent.
For example, suppose that in the response Amazon Lex sends this message: "What size pizza would you like?". A user might reply with the slot value (e.g., "medium"). The user might also provide additional information in the response (e.g., "medium thick crust pizza"). Amazon Lex can process such additional information appropriately.
Fulfilled
– Conveys that the Lambda function configured for
the intent has successfully fulfilled the intent.
ReadyForFulfillment
– Conveys that the client has to fulfill
the intent.
Failed
– Conveys that the conversation with the user failed.
This can happen for various reasons including that the user did not provide an appropriate response to prompts from the service (you can configure how many times Amazon Lex can prompt a user for specific information), or the Lambda function failed to fulfill the intent.
Returns a reference to this object so that method calls can be chained together.
Constraints:
Allowed Values: ElicitIntent, ConfirmIntent, ElicitSlot,
Fulfilled, ReadyForFulfillment, Failed
dialogState
-
Identifies the current state of the user interaction. Amazon
Lex returns one of the following values as
dialogState
. The client can optionally use this
information to customize the user interface.
ElicitIntent
– Amazon Lex wants to elicit user
intent.
For example, a user might utter an intent ("I want to order a pizza"). If Amazon Lex cannot infer the user intent from this utterance, it will return this dialogState.
ConfirmIntent
– Amazon Lex is expecting a "yes"
or "no" response.
For example, Amazon Lex wants user confirmation before fulfilling an intent.
Instead of a simple "yes" or "no," a user might respond with additional information. For example, "yes, but make it thick crust pizza" or "no, I want to order a drink". Amazon Lex can process such additional information (in these examples, update the crust type slot value, or change intent from OrderPizza to OrderDrink).
ElicitSlot
– Amazon Lex is expecting a slot value
for the current intent.
For example, suppose that in the response Amazon Lex sends this message: "What size pizza would you like?". A user might reply with the slot value (e.g., "medium"). The user might also provide additional information in the response (e.g., "medium thick crust pizza"). Amazon Lex can process such additional information appropriately.
Fulfilled
– Conveys that the Lambda function
configured for the intent has successfully fulfilled the
intent.
ReadyForFulfillment
– Conveys that the client has
to fulfill the intent.
Failed
– Conveys that the conversation with the
user failed.
This can happen for various reasons including that the user did not provide an appropriate response to prompts from the service (you can configure how many times Amazon Lex can prompt a user for specific information), or the Lambda function failed to fulfill the intent.
DialogState
public void setDialogState(DialogState dialogState)
Identifies the current state of the user interaction. Amazon Lex returns
one of the following values as dialogState
. The client can
optionally use this information to customize the user interface.
ElicitIntent
– Amazon Lex wants to elicit user intent.
For example, a user might utter an intent ("I want to order a pizza"). If Amazon Lex cannot infer the user intent from this utterance, it will return this dialogState.
ConfirmIntent
– Amazon Lex is expecting a "yes" or "no"
response.
For example, Amazon Lex wants user confirmation before fulfilling an intent.
Instead of a simple "yes" or "no," a user might respond with additional information. For example, "yes, but make it thick crust pizza" or "no, I want to order a drink". Amazon Lex can process such additional information (in these examples, update the crust type slot value, or change intent from OrderPizza to OrderDrink).
ElicitSlot
– Amazon Lex is expecting a slot value for the
current intent.
For example, suppose that in the response Amazon Lex sends this message: "What size pizza would you like?". A user might reply with the slot value (e.g., "medium"). The user might also provide additional information in the response (e.g., "medium thick crust pizza"). Amazon Lex can process such additional information appropriately.
Fulfilled
– Conveys that the Lambda function configured for
the intent has successfully fulfilled the intent.
ReadyForFulfillment
– Conveys that the client has to fulfill
the intent.
Failed
– Conveys that the conversation with the user failed.
This can happen for various reasons including that the user did not provide an appropriate response to prompts from the service (you can configure how many times Amazon Lex can prompt a user for specific information), or the Lambda function failed to fulfill the intent.
Constraints:
Allowed Values: ElicitIntent, ConfirmIntent, ElicitSlot,
Fulfilled, ReadyForFulfillment, Failed
dialogState
-
Identifies the current state of the user interaction. Amazon
Lex returns one of the following values as
dialogState
. The client can optionally use this
information to customize the user interface.
ElicitIntent
– Amazon Lex wants to elicit user
intent.
For example, a user might utter an intent ("I want to order a pizza"). If Amazon Lex cannot infer the user intent from this utterance, it will return this dialogState.
ConfirmIntent
– Amazon Lex is expecting a "yes"
or "no" response.
For example, Amazon Lex wants user confirmation before fulfilling an intent.
Instead of a simple "yes" or "no," a user might respond with additional information. For example, "yes, but make it thick crust pizza" or "no, I want to order a drink". Amazon Lex can process such additional information (in these examples, update the crust type slot value, or change intent from OrderPizza to OrderDrink).
ElicitSlot
– Amazon Lex is expecting a slot value
for the current intent.
For example, suppose that in the response Amazon Lex sends this message: "What size pizza would you like?". A user might reply with the slot value (e.g., "medium"). The user might also provide additional information in the response (e.g., "medium thick crust pizza"). Amazon Lex can process such additional information appropriately.
Fulfilled
– Conveys that the Lambda function
configured for the intent has successfully fulfilled the
intent.
ReadyForFulfillment
– Conveys that the client has
to fulfill the intent.
Failed
– Conveys that the conversation with the
user failed.
This can happen for various reasons including that the user did not provide an appropriate response to prompts from the service (you can configure how many times Amazon Lex can prompt a user for specific information), or the Lambda function failed to fulfill the intent.
DialogState
public PostTextResult withDialogState(DialogState dialogState)
Identifies the current state of the user interaction. Amazon Lex returns
one of the following values as dialogState
. The client can
optionally use this information to customize the user interface.
ElicitIntent
– Amazon Lex wants to elicit user intent.
For example, a user might utter an intent ("I want to order a pizza"). If Amazon Lex cannot infer the user intent from this utterance, it will return this dialogState.
ConfirmIntent
– Amazon Lex is expecting a "yes" or "no"
response.
For example, Amazon Lex wants user confirmation before fulfilling an intent.
Instead of a simple "yes" or "no," a user might respond with additional information. For example, "yes, but make it thick crust pizza" or "no, I want to order a drink". Amazon Lex can process such additional information (in these examples, update the crust type slot value, or change intent from OrderPizza to OrderDrink).
ElicitSlot
– Amazon Lex is expecting a slot value for the
current intent.
For example, suppose that in the response Amazon Lex sends this message: "What size pizza would you like?". A user might reply with the slot value (e.g., "medium"). The user might also provide additional information in the response (e.g., "medium thick crust pizza"). Amazon Lex can process such additional information appropriately.
Fulfilled
– Conveys that the Lambda function configured for
the intent has successfully fulfilled the intent.
ReadyForFulfillment
– Conveys that the client has to fulfill
the intent.
Failed
– Conveys that the conversation with the user failed.
This can happen for various reasons including that the user did not provide an appropriate response to prompts from the service (you can configure how many times Amazon Lex can prompt a user for specific information), or the Lambda function failed to fulfill the intent.
Returns a reference to this object so that method calls can be chained together.
Constraints:
Allowed Values: ElicitIntent, ConfirmIntent, ElicitSlot,
Fulfilled, ReadyForFulfillment, Failed
dialogState
-
Identifies the current state of the user interaction. Amazon
Lex returns one of the following values as
dialogState
. The client can optionally use this
information to customize the user interface.
ElicitIntent
– Amazon Lex wants to elicit user
intent.
For example, a user might utter an intent ("I want to order a pizza"). If Amazon Lex cannot infer the user intent from this utterance, it will return this dialogState.
ConfirmIntent
– Amazon Lex is expecting a "yes"
or "no" response.
For example, Amazon Lex wants user confirmation before fulfilling an intent.
Instead of a simple "yes" or "no," a user might respond with additional information. For example, "yes, but make it thick crust pizza" or "no, I want to order a drink". Amazon Lex can process such additional information (in these examples, update the crust type slot value, or change intent from OrderPizza to OrderDrink).
ElicitSlot
– Amazon Lex is expecting a slot value
for the current intent.
For example, suppose that in the response Amazon Lex sends this message: "What size pizza would you like?". A user might reply with the slot value (e.g., "medium"). The user might also provide additional information in the response (e.g., "medium thick crust pizza"). Amazon Lex can process such additional information appropriately.
Fulfilled
– Conveys that the Lambda function
configured for the intent has successfully fulfilled the
intent.
ReadyForFulfillment
– Conveys that the client has
to fulfill the intent.
Failed
– Conveys that the conversation with the
user failed.
This can happen for various reasons including that the user did not provide an appropriate response to prompts from the service (you can configure how many times Amazon Lex can prompt a user for specific information), or the Lambda function failed to fulfill the intent.
DialogState
public String getSlotToElicit()
If the dialogState
value is ElicitSlot
, returns
the name of the slot for which Amazon Lex is eliciting a value.
If the dialogState
value is ElicitSlot
,
returns the name of the slot for which Amazon Lex is eliciting a
value.
public void setSlotToElicit(String slotToElicit)
If the dialogState
value is ElicitSlot
, returns
the name of the slot for which Amazon Lex is eliciting a value.
slotToElicit
-
If the dialogState
value is
ElicitSlot
, returns the name of the slot for
which Amazon Lex is eliciting a value.
public PostTextResult withSlotToElicit(String slotToElicit)
If the dialogState
value is ElicitSlot
, returns
the name of the slot for which Amazon Lex is eliciting a value.
Returns a reference to this object so that method calls can be chained together.
slotToElicit
-
If the dialogState
value is
ElicitSlot
, returns the name of the slot for
which Amazon Lex is eliciting a value.
public ResponseCard getResponseCard()
Represents the options that the user has to respond to the current prompt. Response Card can come from the bot configuration (in the Amazon Lex console, choose the settings button next to a slot) or from a code hook (Lambda function).
Represents the options that the user has to respond to the current prompt. Response Card can come from the bot configuration (in the Amazon Lex console, choose the settings button next to a slot) or from a code hook (Lambda function).
public void setResponseCard(ResponseCard responseCard)
Represents the options that the user has to respond to the current prompt. Response Card can come from the bot configuration (in the Amazon Lex console, choose the settings button next to a slot) or from a code hook (Lambda function).
responseCard
- Represents the options that the user has to respond to the current prompt. Response Card can come from the bot configuration (in the Amazon Lex console, choose the settings button next to a slot) or from a code hook (Lambda function).
public PostTextResult withResponseCard(ResponseCard responseCard)
Represents the options that the user has to respond to the current prompt. Response Card can come from the bot configuration (in the Amazon Lex console, choose the settings button next to a slot) or from a code hook (Lambda function).
Returns a reference to this object so that method calls can be chained together.
responseCard
- Represents the options that the user has to respond to the current prompt. Response Card can come from the bot configuration (in the Amazon Lex console, choose the settings button next to a slot) or from a code hook (Lambda function).
public String toString()
toString
in class Object
Object.toString()
Copyright © 2018. All rights reserved.