Expand description
Data structures used by operation inputs/outputs.
Modules§
Structs§
- Active
Context A context is a variable that contains information about the current state of the conversation between a user and Amazon Lex. Context can be set automatically by Amazon Lex when an intent is fulfilled, or it can be set at runtime using the
PutContent
,PutText
, orPutSession
operation.- Active
Context Time ToLive The length of time or number of turns that a context remains active.
- Button
Represents an option to be shown on the client platform (Facebook, Slack, etc.)
- Dialog
Action Describes the next action that the bot should take in its interaction with the user and provides information about the context in which the action takes place. Use the
DialogAction
data type to set the interaction to a specific state, or to return the interaction to a previous state.- Generic
Attachment Represents an option rendered to the user when a prompt is shown. It could be an image, a button, a link, or text.
- Intent
Confidence Provides a score that indicates the confidence that Amazon Lex has that an intent is the one that satisfies the user's intent.
- Intent
Summary Provides information about the state of an intent. You can use this information to get the current state of an intent so that you can process the intent, or so that you can return the intent to its previous state.
- Predicted
Intent An intent that Amazon Lex suggests satisfies the user's intent. Includes the name of the intent, the confidence that Amazon Lex has that the user's intent is satisfied, and the slots defined for the intent.
- Response
Card If you configure a response card when creating your bots, Amazon Lex substitutes the session attributes and slot values that are available, and then returns it. The response card can also come from a Lambda function (
dialogCodeHook
andfulfillmentActivity
on an intent).- Sentiment
Response The sentiment expressed in an utterance.
When the bot is configured to send utterances to Amazon Comprehend for sentiment analysis, this field structure contains the result of the analysis.
Enums§
- Confirmation
Status - When writing a match expression against
ConfirmationStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Content
Type - When writing a match expression against
ContentType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Dialog
Action Type - When writing a match expression against
DialogActionType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Dialog
State - When writing a match expression against
DialogState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Fulfillment
State - When writing a match expression against
FulfillmentState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Message
Format Type - When writing a match expression against
MessageFormatType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.