public class PostContentResult extends Object implements Serializable
| Constructor and Description |
|---|
PostContentResult() |
| Modifier and Type | Method and Description |
|---|---|
boolean |
equals(Object obj) |
InputStream |
getAudioStream()
The prompt (or statement) to convey to the user.
|
String |
getContentType()
Content type as specified in the
Accept HTTP header in the
request. |
String |
getDialogState()
Identifies the current state of the user interaction.
|
String |
getInputTranscript()
Transcript of the voice input to the operation.
|
String |
getIntentName()
Current user intent that Amazon Lex is aware of.
|
String |
getMessage()
Message to convey to the user.
|
Map<String,String> |
getSessionAttributes()
Map of key/value pairs representing the session-specific context
information.
|
Map<String,String> |
getSlots()
Map of zero or more intent slots (name/value pairs) Amazon Lex detected
from the user input during 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 |
setAudioStream(InputStream audioStream)
The prompt (or statement) to convey to the user.
|
void |
setContentType(String contentType)
Content type as specified in the
Accept HTTP header in the
request. |
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 |
setInputTranscript(String inputTranscript)
Transcript of the voice input to the operation.
|
void |
setIntentName(String intentName)
Current user intent that Amazon Lex is aware of.
|
void |
setMessage(String message)
Message to convey to the user.
|
void |
setSessionAttributes(Map<String,String> sessionAttributes)
Map of key/value pairs representing the session-specific context
information.
|
void |
setSlots(Map<String,String> slots)
Map of zero or more intent slots (name/value pairs) Amazon Lex detected
from the user input during 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.
|
PostContentResult |
withAudioStream(InputStream audioStream)
The prompt (or statement) to convey to the user.
|
PostContentResult |
withContentType(String contentType)
Content type as specified in the
Accept HTTP header in the
request. |
PostContentResult |
withDialogState(DialogState dialogState)
Identifies the current state of the user interaction.
|
PostContentResult |
withDialogState(String dialogState)
Identifies the current state of the user interaction.
|
PostContentResult |
withInputTranscript(String inputTranscript)
Transcript of the voice input to the operation.
|
PostContentResult |
withIntentName(String intentName)
Current user intent that Amazon Lex is aware of.
|
PostContentResult |
withMessage(String message)
Message to convey to the user.
|
PostContentResult |
withSessionAttributes(Map<String,String> sessionAttributes)
Map of key/value pairs representing the session-specific context
information.
|
PostContentResult |
withSlots(Map<String,String> slots)
Map of zero or more intent slots (name/value pairs) Amazon Lex detected
from the user input during the conversation.
|
PostContentResult |
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 getContentType()
Content type as specified in the Accept HTTP header in the
request.
Content type as specified in the Accept HTTP header
in the request.
public void setContentType(String contentType)
Content type as specified in the Accept HTTP header in the
request.
contentType -
Content type as specified in the Accept HTTP
header in the request.
public PostContentResult withContentType(String contentType)
Content type as specified in the Accept HTTP header in the
request.
Returns a reference to this object so that method calls can be chained together.
contentType -
Content type as specified in the Accept HTTP
header in the request.
public String getIntentName()
Current user intent that Amazon Lex is aware of.
Current user intent that Amazon Lex is aware of.
public void setIntentName(String intentName)
Current user intent that Amazon Lex is aware of.
intentName - Current user intent that Amazon Lex is aware of.
public PostContentResult withIntentName(String intentName)
Current user intent that Amazon Lex is aware of.
Returns a reference to this object so that method calls can be chained together.
intentName - Current user intent that Amazon Lex is aware of.
public Map<String,String> getSlots()
Map of zero or more intent slots (name/value pairs) Amazon Lex detected from the user input during the conversation.
Map of zero or more intent slots (name/value pairs) Amazon Lex detected from the user input during the conversation.
public void setSlots(Map<String,String> slots)
Map of zero or more intent slots (name/value pairs) Amazon Lex detected from the user input during the conversation.
slots - Map of zero or more intent slots (name/value pairs) Amazon Lex detected from the user input during the conversation.
public PostContentResult withSlots(Map<String,String> slots)
Map of zero or more intent slots (name/value pairs) Amazon Lex detected from the user input during the conversation.
Returns a reference to this object so that method calls can be chained together.
slots - Map of zero or more intent slots (name/value pairs) Amazon Lex detected from the user input during the conversation.
public Map<String,String> getSessionAttributes()
Map of key/value pairs representing the session-specific context information.
Map of key/value pairs representing the session-specific context information.
public void setSessionAttributes(Map<String,String> sessionAttributes)
Map of key/value pairs representing the session-specific context information.
sessionAttributes - Map of key/value pairs representing the session-specific context information.
public PostContentResult withSessionAttributes(Map<String,String> sessionAttributes)
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 - Map of key/value pairs representing the session-specific context information.
public String getMessage()
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 if 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 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 if 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)
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 if 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 -
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 if 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 PostContentResult withMessage(String message)
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 if 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 -
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 if 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 the user's intent.
Consider the following examples:
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 dialog state.
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" response, a user might respond with additional information. For example, "yes, but make it a 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 or change the intent from OrderPizza to OrderDrink).
ElicitSlot – Amazon Lex is expecting the value of a slot 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 has
successfully fulfilled the intent.
ReadyForFulfillment – Conveys that the client has to
fullfill the request.
Failed – Conveys that the conversation with the user failed.
This can happen for various reasons, including that the user does 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 if the Lambda function fails 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 the user's
intent. Consider the following examples:
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 dialog state.
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" response, a user might respond with additional information. For example, "yes, but make it a 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 or change the intent from OrderPizza to OrderDrink).
ElicitSlot – Amazon Lex is expecting the value of a
slot 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 has
successfully fulfilled the intent.
ReadyForFulfillment – Conveys that the client has to
fullfill the request.
Failed – Conveys that the conversation with the user
failed.
This can happen for various reasons, including that the user does 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 if the Lambda function fails to fulfill the intent.
DialogStatepublic 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 the user's intent.
Consider the following examples:
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 dialog state.
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" response, a user might respond with additional information. For example, "yes, but make it a 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 or change the intent from OrderPizza to OrderDrink).
ElicitSlot – Amazon Lex is expecting the value of a slot 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 has
successfully fulfilled the intent.
ReadyForFulfillment – Conveys that the client has to
fullfill the request.
Failed – Conveys that the conversation with the user failed.
This can happen for various reasons, including that the user does 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 if the Lambda function fails 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 the
user's intent. Consider the following examples:
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 dialog state.
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" response, a user might respond with additional information. For example, "yes, but make it a 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 or change the intent from OrderPizza to OrderDrink).
ElicitSlot – Amazon Lex is expecting the value of
a slot 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 has
successfully fulfilled the intent.
ReadyForFulfillment – Conveys that the client has
to fullfill the request.
Failed – Conveys that the conversation with the
user failed.
This can happen for various reasons, including that the user does 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 if the Lambda function fails to fulfill the intent.
DialogStatepublic PostContentResult 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 the user's intent.
Consider the following examples:
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 dialog state.
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" response, a user might respond with additional information. For example, "yes, but make it a 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 or change the intent from OrderPizza to OrderDrink).
ElicitSlot – Amazon Lex is expecting the value of a slot 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 has
successfully fulfilled the intent.
ReadyForFulfillment – Conveys that the client has to
fullfill the request.
Failed – Conveys that the conversation with the user failed.
This can happen for various reasons, including that the user does 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 if the Lambda function fails 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 the
user's intent. Consider the following examples:
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 dialog state.
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" response, a user might respond with additional information. For example, "yes, but make it a 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 or change the intent from OrderPizza to OrderDrink).
ElicitSlot – Amazon Lex is expecting the value of
a slot 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 has
successfully fulfilled the intent.
ReadyForFulfillment – Conveys that the client has
to fullfill the request.
Failed – Conveys that the conversation with the
user failed.
This can happen for various reasons, including that the user does 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 if the Lambda function fails to fulfill the intent.
DialogStatepublic 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 the user's intent.
Consider the following examples:
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 dialog state.
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" response, a user might respond with additional information. For example, "yes, but make it a 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 or change the intent from OrderPizza to OrderDrink).
ElicitSlot – Amazon Lex is expecting the value of a slot 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 has
successfully fulfilled the intent.
ReadyForFulfillment – Conveys that the client has to
fullfill the request.
Failed – Conveys that the conversation with the user failed.
This can happen for various reasons, including that the user does 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 if the Lambda function fails 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 the
user's intent. Consider the following examples:
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 dialog state.
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" response, a user might respond with additional information. For example, "yes, but make it a 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 or change the intent from OrderPizza to OrderDrink).
ElicitSlot – Amazon Lex is expecting the value of
a slot 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 has
successfully fulfilled the intent.
ReadyForFulfillment – Conveys that the client has
to fullfill the request.
Failed – Conveys that the conversation with the
user failed.
This can happen for various reasons, including that the user does 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 if the Lambda function fails to fulfill the intent.
DialogStatepublic PostContentResult 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 the user's intent.
Consider the following examples:
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 dialog state.
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" response, a user might respond with additional information. For example, "yes, but make it a 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 or change the intent from OrderPizza to OrderDrink).
ElicitSlot – Amazon Lex is expecting the value of a slot 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 has
successfully fulfilled the intent.
ReadyForFulfillment – Conveys that the client has to
fullfill the request.
Failed – Conveys that the conversation with the user failed.
This can happen for various reasons, including that the user does 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 if the Lambda function fails 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 the
user's intent. Consider the following examples:
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 dialog state.
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" response, a user might respond with additional information. For example, "yes, but make it a 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 or change the intent from OrderPizza to OrderDrink).
ElicitSlot – Amazon Lex is expecting the value of
a slot 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 has
successfully fulfilled the intent.
ReadyForFulfillment – Conveys that the client has
to fullfill the request.
Failed – Conveys that the conversation with the
user failed.
This can happen for various reasons, including that the user does 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 if the Lambda function fails to fulfill the intent.
DialogStatepublic 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 PostContentResult 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 String getInputTranscript()
Transcript of the voice input to the operation.
Transcript of the voice input to the operation.
public void setInputTranscript(String inputTranscript)
Transcript of the voice input to the operation.
inputTranscript - Transcript of the voice input to the operation.
public PostContentResult withInputTranscript(String inputTranscript)
Transcript of the voice input to the operation.
Returns a reference to this object so that method calls can be chained together.
inputTranscript - Transcript of the voice input to the operation.
public InputStream getAudioStream()
The prompt (or statement) to convey to the user. This is based on the bot
configuration and context. For example, if Amazon Lex did not understand
the user intent, it sends the clarificationPrompt configured
for the bot. If the intent requires confirmation before taking the
fulfillment action, it sends the confirmationPrompt. Another
example: Suppose that the Lambda function successfully fulfilled the
intent, and sent a message to convey to the user. Then Amazon Lex sends
that message in the response.
The prompt (or statement) to convey to the user. This is based on
the bot configuration and context. For example, if Amazon Lex did
not understand the user intent, it sends the
clarificationPrompt configured for the bot. If the
intent requires confirmation before taking the fulfillment
action, it sends the confirmationPrompt. Another
example: Suppose that the Lambda function successfully fulfilled
the intent, and sent a message to convey to the user. Then Amazon
Lex sends that message in the response.
public void setAudioStream(InputStream audioStream)
The prompt (or statement) to convey to the user. This is based on the bot
configuration and context. For example, if Amazon Lex did not understand
the user intent, it sends the clarificationPrompt configured
for the bot. If the intent requires confirmation before taking the
fulfillment action, it sends the confirmationPrompt. Another
example: Suppose that the Lambda function successfully fulfilled the
intent, and sent a message to convey to the user. Then Amazon Lex sends
that message in the response.
audioStream -
The prompt (or statement) to convey to the user. This is based
on the bot configuration and context. For example, if Amazon
Lex did not understand the user intent, it sends the
clarificationPrompt configured for the bot. If
the intent requires confirmation before taking the fulfillment
action, it sends the confirmationPrompt. Another
example: Suppose that the Lambda function successfully
fulfilled the intent, and sent a message to convey to the
user. Then Amazon Lex sends that message in the response.
public PostContentResult withAudioStream(InputStream audioStream)
The prompt (or statement) to convey to the user. This is based on the bot
configuration and context. For example, if Amazon Lex did not understand
the user intent, it sends the clarificationPrompt configured
for the bot. If the intent requires confirmation before taking the
fulfillment action, it sends the confirmationPrompt. Another
example: Suppose that the Lambda function successfully fulfilled the
intent, and sent a message to convey to the user. Then Amazon Lex sends
that message in the response.
Returns a reference to this object so that method calls can be chained together.
audioStream -
The prompt (or statement) to convey to the user. This is based
on the bot configuration and context. For example, if Amazon
Lex did not understand the user intent, it sends the
clarificationPrompt configured for the bot. If
the intent requires confirmation before taking the fulfillment
action, it sends the confirmationPrompt. Another
example: Suppose that the Lambda function successfully
fulfilled the intent, and sent a message to convey to the
user. Then Amazon Lex sends that message in the response.
public String toString()
toString in class ObjectObject.toString()Copyright © 2018. All rights reserved.