Module aws_sdk_lexmodelsv2::types
source · Expand description
Data structures used by operation inputs/outputs.
Modules§
- Builders
- Error types that Amazon Lex Model Building V2 can respond with.
Structs§
The active context used in the test execution.
Provides settings that enable advanced recognition settings for slot values.
The information about the agent turn in a test set execution.
The specification of an agent turn.
Filters responses returned by the
ListAggregatedUtterances
operation.Specifies attributes for sorting a list of utterances.
Provides summary information for aggregated utterances. The
ListAggregatedUtterances
operations combines all instances of the same utterance into a single aggregated summary.Specifies the allowed input types.
Contains the time metric, interval, and method by which to bin the analytics data.
An object containing the criterion by which to bin the results and the value that defines that bin.
Contains fields describing a condition by which to filter the intents. The expression may be understood as
name
operator
values
. For example:Contains the category by which the intent analytics were grouped and a member of that category.
Contains the category by which to group the intents.
Contains the metric and the summary statistic you want to calculate, and the order in which to sort the results, for the intents in the bot.
An object containing the results for the intent metric you requested.
An object containing information about the requested path.
An object containing the results for the intent metrics you requested and the bin and/or group(s) they refer to, if applicable.
Contains fields describing a condition by which to filter the intent stages. The expression may be understood as
name
operator
values
. For example:Contains the category by which the intent stage analytics and the values for that category were grouped.
Contains the category by which to group the intent stages.
Contains the metric and the summary statistic you want to calculate, and the order in which to sort the results, for the intent stages across the user sessions with the bot.
An object containing the results for an intent stage metric you requested.
An object containing the results for the intent stage metrics you requested and the bin and/or group they refer to, if applicable.
Contains fields describing a condition by which to filter the paths. The expression may be understood as
name
operator
values
. For example:Contains fields describing a condition by which to filter the sessions. The expression may be understood as
name
operator
values
. For example:Contains the category by which the session analytics were grouped and a member of that category.
Contains the category by which to group the sessions.
Contains the metric and the summary statistic you want to calculate, and the order in which to sort the results, for the user sessions with the bot.
An object containing the results for a session metric you requested.
An object containing the results for the session metrics you requested and the bin and/or group(s) they refer to, if applicable.
An object that specifies the last used intent at the time of the utterance as an attribute to return.
An object containing the intent that the bot mapped the utterance to.
Contains fields describing a condition by which to filter the utterances. The expression may be understood as
name
operator
values
. For example:Contains the category by which the utterance analytics were grouped and the values for that category.
Contains the category by which to group the utterances.
Contains the metric and the summary statistic you want to calculate, and the order in which to sort the results, for the utterances across the user sessions with the bot.
An object containing the results for the utterance metric you requested.
An object containing the results for the utterance metrics you requested and the bin and/or group(s) they refer to, if applicable.
The object containing information that associates the recommended intent/slot type with a conversation.
Filters to search for the associated transcript.
Specifies the audio and DTMF input specification.
The location of audio log files collected when conversation logging is enabled for a bot.
Settings for logging audio of conversations between Amazon Lex and a user. You specify whether to log audio and the Amazon S3 bucket where the audio file is stored.
Specifies the audio input specifications.
Contains details about the configuration of a Amazon Bedrock knowledge base.
Contains information about the Amazon Bedrock model used to interpret the prompt used in descriptive bot building.
Provides a record of an event that affects a bot alias. For example, when the version of a bot that the alias points to changes.
Specifies settings that are unique to a locale. For example, you can use different Lambda function depending on the bot's locale.
Contains information about all the aliases replication statuses applicable for global resiliency.
Summary information about bot aliases returned from the ListBotAliases operation.
The target Amazon S3 location for the test set execution using a bot alias.
Provides the identity of a the bot that was exported.
Filters the responses returned by the
ListBots
operation.Provides the bot parameters required for importing a bot.
Provides the bot locale parameters required for exporting a bot locale.
Filters responses returned by the
ListBotLocales
operation.Provides information about an event that occurred affecting the bot locale.
Provides the bot locale parameters required for importing a bot locale.
Specifies attributes for sorting a list of bot locales.
Summary information about bot locales returned by the ListBotLocales operation.
A bot that is a member of a network of bots.
A statistical summary of the bot recommendation results.
The object representing the URL of the bot definition, the URL of the associated transcript, and a statistical summary of the bot recommendation results.
A summary of the bot recommendation.
Contains summary information about all the replication statuses applicable for global resiliency.
Specifies attributes for sorting a list of bots.
Summary information about a bot returned by the ListBots operation.
The version of a bot used for a bot locale.
The sort category for the version replicated bots.
Contains summary information for all the version replication statuses applicable for Global resiliency.
Specifies attributes for sorting a list of bot versions.
Summary information about a bot version returned by the ListBotVersions operation.
Contains specifications about the Amazon Lex build time generative AI capabilities from Amazon Bedrock that you can turn on for your bot.
Specifies attributes for sorting a list of built-in intents.
Provides summary information about a built-in intent for the ListBuiltInIntents operation.
Specifies attributes for sorting a list of built-in slot types.
Provides summary information about a built-in slot type for the ListBuiltInSlotTypes operation.
Describes a button to use on a response card used to gather slot values from a user.
The Amazon CloudWatch Logs log group where the text and metadata logs are delivered. The log group must exist before you enable logging.
Contains information about code hooks that Amazon Lex calls during a conversation.
A composite slot is a combination of two or more slots that capture multiple pieces of information in a single user input.
Provides an expression that evaluates to true or false.
A set of actions that Amazon Lex should run if the condition is matched.
Provides a list of conditional branches. Branches are evaluated in the order that they are entered in the list. The first branch with a condition that evaluates to true is executed. The last branch in the list is the default branch. The default branch should not have any condition expression. The default branch is executed if no other branch has a matching condition.
The item listing the evaluation of intent level success or failure.
The conversation level details of the conversation used in the test set.
The slots used for the slot resolution in the conversation.
The test result evaluation item at the conversation level.
The test set results data at the conversation level.
The selection to filter the test set results data at the conversation level.
Configures conversation logging that saves audio, text, and metadata for the conversations with your users.
The data source that uses conversation logs.
The selected data source to filter the conversation log.
A custom response string that Amazon Lex sends to your application. You define the content and structure the string.
The unique entry identifier for the custom vocabulary items.
Provides the parameters required for exporting a custom vocabulary.
Provides the parameters required for importing a custom vocabulary.
The unique custom vocabulary item from the custom vocabulary list.
By default, data stored by Amazon Lex is encrypted. The
DataPrivacy
structure provides settings that determine how Amazon Lex handles special cases of securing the data for your bot.Contains details about the configuration of the knowledge store used for the
AMAZON.QnAIntent
. You must have already created the knowledge store and indexed the documents within it.The object used for specifying the data range that the customer wants Amazon Lex to read through in the input transcripts.
A set of actions that Amazon Lex should run if none of the other conditions are met.
Contains specifications for the descriptive bot building feature.
Defines the action that the bot executes at runtime when the conversation reaches this step.
Settings that specify the dialog code hook that is called by Amazon Lex at a step of the conversation.
Settings that determine the Lambda function that Amazon Lex uses for processing user responses.
The current state of the conversation with the user.
Specifies the DTMF input specifications.
Settings that specify the dialog code hook that is called by Amazon Lex between eliciting slot values.
The object representing the passwords that were used to encrypt the data related to the bot recommendation, as well as the KMS key ARN used to encrypt the associated metadata.
Contains the names of the fields used for an exact response to the user.
Details about an error in an execution of a test set.
Filters the response form the ListExports operation
Provides information about the bot or bot locale that you want to export. You can specify the
botExportSpecification
or thebotLocaleExportSpecification
, but not both.Provides information about sorting a list of exports.
Provides summary information about an export in an export list.
Provides information about the external source of the slot type's definition.
The unique failed custom vocabulary item from the custom vocabulary list.
Determines if a Lambda function should be invoked for a specific intent.
Provides settings for a message that is sent to the user when a fulfillment Lambda function starts running.
Provides settings for a message that is sent periodically to the user while a fulfillment Lambda function is running.
Provides information for updating the user on the progress of fulfilling an intent.
Specifies the attribute and method by which to sort the generation request information.
Contains information about a generation request made for the bot locale.
Contains specifications about the generative AI capabilities from Amazon Bedrock that you can turn on for your bot.
Settings requried for a slot type based on a grammar that you provide.
Describes the Amazon S3 bucket name and location for the grammar that is the source for the slot type.
A card that is shown to the user by a messaging platform. You define the contents of the card, the card is displayed by the platform.
Filters the response from the ListImports operation.
Provides information about the bot or bot locale that you want to import. You can specify the
botImportSpecification
or thebotLocaleImportSpecification
, but not both.Provides information for sorting a list of imports.
Provides summary information about an import in an import list.
Configuration setting for a response sent to the user before Amazon Lex starts eliciting slots.
A context that must be active for an intent to be selected by Amazon Lex.
Specifications for the current state of the dialog between the user and the bot in the test set.
Information for an intent that is classified by the test workbench.
The number of items in the intent classification test.
Information for the results of the intent classification test.
Provides a statement the Amazon Lex conveys to the user when the intent is successfully fulfilled.
Provides a prompt for making sure that the user is ready for the intent to be fulfilled.
Filters the response from the
ListIntents
operation.Information about intent-level slot resolution in a test result.
Indicates the success or failure of slots at the intent level.
Override settings to configure the intent state.
Specifies attributes for sorting a list of intents.
The object that contains the statistical summary of recommended intents associated with the bot recommendation.
Summary information about an intent returned by the
ListIntents
operation.An object containing the name of an intent that was invoked.
Provides configuration information for the
AMAZON.KendraSearchIntent
intent. When you use this intent, Amazon Lex searches the specified Amazon Kendra index and returns documents from the index that match the user's utterance.Specifies a Lambda function that verifies requests to a bot or fulfills the user's request to a bot.
The object that contains transcript filter details that are associated with a bot recommendation.
The object that provides message text and its type.
Provides one or more messages that Amazon Lex should send to the user.
Indicates whether a slot can return multiple values.
The new custom vocabulary item from the custom vocabulary list.
Determines whether Amazon Lex obscures slot values in conversation logs.
Contains details about the configuration of the Amazon OpenSearch Service database used for the
AMAZON.QnAIntent
.Describes a session context that is activated when an intent is fulfilled.
Information about the overall results for a test execution result.
Information about the overall test results.
A network of bots.
The object that contains a path format that will be applied when Amazon Lex reads the transcript file in the bucket you provide. Specify this object if you only want Lex to read a subset of files in your Amazon S3 bucket.
Defines an ASCII text message to send to the user.
Specifies next steps to run after the dialog code hook finishes.
Provides a setting that determines whether the post-fulfillment response is sent to the user. For more information, see https://docs.aws.amazon.com/lexv2/latest/dg/streaming-progress.html#progress-complete
The IAM principal that you allowing or denying access to an Amazon Lex action. You must provide a
service
or anarn
, but not both in the same statement. For more information, see AWS JSON policy elements: Principal .Specifies the settings on a prompt attempt.
Specifies a list of message groups that Amazon Lex sends to a user to elicit a response.
Details about the the configuration of the built-in
Amazon.QnAIntent
.Contains details about the configuration of the Amazon Kendra index used for the
AMAZON.QnAIntent
.An object that contains a summary of a recommended intent.
Specifies the time window that utterance statistics are returned for. The time window is always relative to the last time that the that utterances were aggregated. For example, if the
ListAggregatedUtterances
operation is called at 1600, the time window is set to 1 hour, and the last refresh time was 1530, only utterances made between 1430 and 1530 are returned.Specifies a list of message groups that Amazon Lex uses to respond the user input.
Provides an array of phrases that should be given preference when resolving values for a slot.
Provides the phrase that Amazon Lex should look for in the user's input to the bot.
You can provide Amazon Lex with hints to the phrases that a customer is likely to use for a slot. When a slot with hints is resolved, the phrases in the runtime hints are preferred in the resolution. You can provide hints for a maximum of 100 intents. You can provide a maximum of 100 slots.
Contains specifications about the Amazon Lex runtime generative AI capabilities from Amazon Bedrock that you can turn on for your bot.
Specifies an Amazon S3 bucket for logging audio conversations
The object representing the Amazon S3 bucket containing the transcript, as well as the associated metadata.
A sample utterance that invokes an intent or respond to a slot elicitation prompt.
Contains specifications for the sample utterance generation feature.
Defines one of the values for a slot type.
Determines whether Amazon Lex will use Amazon Comprehend to detect the sentiment of user utterances.
An object specifying the measure and method by which to sort the session analytics data.
An object containing information about a specific session.
Settings used when Amazon Lex successfully captures a slot value from a user.
Specifies the default value to use when a user doesn't provide a value for a slot.
Defines a list of values that Amazon Lex should use as the default value for a slot.
Filters the response from the
ListSlots
operation.Sets the priority that Amazon Lex should use when eliciting slot values from a user.
Contains specifications for the assisted slot resolution feature.
Contains information about whether assisted slot resolution is turned on for the slot or not.
Information about the success and failure rate of slot resolution in the results of a test execution.
Information about the counts for a slot resolution in the results of a test execution.
Specifies attributes for sorting a list of bots.
Summary information about a slot, a value that the bot elicits from the user.
Filters the response from the
ListSlotTypes
operation.Specifies attributes for sorting a list of slot types.
The object that contains the statistical summary of the recommended slot type associated with the bot recommendation.
Provides summary information about a slot type.
Each slot type can have a set of values. Each
SlotTypeValue
represents a value that the slot type can take.The value to set in a slot.
Specifies the elicitation setting details eliciting a slot.
The slot values that Amazon Lex uses when it sets slot values in a dialog step.
Provides a regular expression used to validate the value of a slot.
Contains settings used by Amazon Lex to select a slot value.
Subslot specifications.
Defines a Speech Synthesis Markup Language (SSML) prompt.
Defines the messages that Amazon Lex sends to a user to remind them that the bot is waiting for a response.
Specifications for the constituent sub slots and the expression for the composite slot.
Subslot type composition.
Subslot elicitation settings.
Contains information about the method by which to filter the results of the test execution.
Contains the results of the test execution, grouped by type of results. See Test result details">Test results details for details about different types of results.
Contains information about the method by which to sort the instances of test executions you have carried out.
Summarizes metadata about the test execution.
Contains information about the bot used for the test execution.
Contains details about the errors in the test set discrepancy report
Contains information about the bot alias used for the test set discrepancy report.
Contains information about the resource used for the test set discrepancy report.
Contains information about the test set that is exported.
Contains information about the data source from which the test set is generated.
Contains information about the Amazon S3 location from which the test set is imported.
Contains information about the test set that is imported.
Contains information about discrepancy in an intent information between the test set and the bot.
Contains information about discrepancy in a slot information between the test set and the bot.
Contains information about the methods by which to sort the test set.
Contains information about the location in which the test set is stored.
Contains summary information about the test set.
Contains information about a turn in a test set.
Contains information about the results of the analysis of a turn in the test set.
Specifies the text input specifications.
Defines the Amazon CloudWatch Logs destination log group for conversation text logs.
Defines settings to enable text conversation logs.
The object representing the filter that Amazon Lex will use to select the appropriate transcript.
Indicates the setting of the location where the transcript is stored.
Contains information about the messages in the turn.
Contains information about the user messages in the turn in the input.
Contains information about the intent that is output for the turn by the test execution.
Contains results that are output for the user turn by the test execution.
Contains the results for the user turn by the test execution.
Contains information about a slot output by the test set execution.
Contains information about the expected and input values for the user turn.
Provides parameters for setting the time window and duration for aggregating utterance data.
Contains information about the audio for an utterance.
An object that contains a response to the utterance from the bot.
An object specifying the measure and method by which to sort the utterance data.
Contains information about input of an utterance.
Contains information about multiple utterances in the results of a test set execution.
Contains information about the utterances in the results of the test set execution.
An object containing information about a specific utterance.
Defines settings for using an Amazon Polly voice to communicate with a user.
Specifies the prompts that Amazon Lex uses while a bot is waiting for customer input.
Enums§
- When writing a match expression against
AggregatedUtterancesFilterName
, 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. - When writing a match expression against
AggregatedUtterancesFilterOperator
, 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. - When writing a match expression against
AggregatedUtterancesSortAttribute
, 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. - When writing a match expression against
AnalyticsBinByName
, 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. - When writing a match expression against
AnalyticsCommonFilterName
, 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. - When writing a match expression against
AnalyticsFilterOperator
, 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. - When writing a match expression against
AnalyticsIntentField
, 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. - When writing a match expression against
AnalyticsIntentFilterName
, 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. - When writing a match expression against
AnalyticsIntentMetricName
, 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. - When writing a match expression against
AnalyticsIntentStageField
, 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. - When writing a match expression against
AnalyticsIntentStageFilterName
, 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. - When writing a match expression against
AnalyticsIntentStageMetricName
, 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. - When writing a match expression against
AnalyticsInterval
, 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. - When writing a match expression against
AnalyticsMetricStatistic
, 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. - When writing a match expression against
AnalyticsModality
, 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. - When writing a match expression against
AnalyticsNodeType
, 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. - When writing a match expression against
AnalyticsSessionField
, 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. - When writing a match expression against
AnalyticsSessionFilterName
, 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. - When writing a match expression against
AnalyticsSessionMetricName
, 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. - When writing a match expression against
AnalyticsSessionSortByName
, 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. - When writing a match expression against
AnalyticsSortOrder
, 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. - When writing a match expression against
AnalyticsUtteranceAttributeName
, 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. - When writing a match expression against
AnalyticsUtteranceField
, 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. - When writing a match expression against
AnalyticsUtteranceFilterName
, 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. - When writing a match expression against
AnalyticsUtteranceMetricName
, 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. - When writing a match expression against
AnalyticsUtteranceSortByName
, 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. - When writing a match expression against
AssociatedTranscriptFilterName
, 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. - When writing a match expression against
AudioRecognitionStrategy
, 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. - When writing a match expression against
BotAliasReplicationStatus
, 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. - When writing a match expression against
BotAliasStatus
, 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. - When writing a match expression against
BotFilterName
, 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. - When writing a match expression against
BotFilterOperator
, 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. - When writing a match expression against
BotLocaleFilterName
, 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. - When writing a match expression against
BotLocaleFilterOperator
, 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. - When writing a match expression against
BotLocaleSortAttribute
, 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. - When writing a match expression against
BotLocaleStatus
, 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. - When writing a match expression against
BotRecommendationStatus
, 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. - When writing a match expression against
BotReplicaStatus
, 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. - When writing a match expression against
BotSortAttribute
, 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. - When writing a match expression against
BotStatus
, 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. - When writing a match expression against
BotType
, 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. - When writing a match expression against
BotVersionReplicaSortAttribute
, 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. - When writing a match expression against
BotVersionReplicationStatus
, 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. - When writing a match expression against
BotVersionSortAttribute
, 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. - When writing a match expression against
BuiltInIntentSortAttribute
, 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. - When writing a match expression against
BuiltInSlotTypeSortAttribute
, 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. - When writing a match expression against
ConversationEndState
, 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. - When writing a match expression against
ConversationLogsInputModeFilter
, 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. - When writing a match expression against
CustomVocabularyStatus
, 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. - 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. - When writing a match expression against
Effect
, 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. - When writing a match expression against
ErrorCode
, 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. - When writing a match expression against
ExportFilterName
, 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. - When writing a match expression against
ExportFilterOperator
, 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. - When writing a match expression against
ExportSortAttribute
, 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. - When writing a match expression against
ExportStatus
, 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. - When writing a match expression against
GenerationSortByAttribute
, 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. - When writing a match expression against
GenerationStatus
, 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. - When writing a match expression against
ImportExportFileFormat
, 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. - When writing a match expression against
ImportFilterName
, 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. - When writing a match expression against
ImportFilterOperator
, 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. - When writing a match expression against
ImportResourceType
, 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. - When writing a match expression against
ImportSortAttribute
, 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. - When writing a match expression against
ImportStatus
, 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. - When writing a match expression against
IntentFilterName
, 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. - When writing a match expression against
IntentFilterOperator
, 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. - When writing a match expression against
IntentSortAttribute
, 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. - When writing a match expression against
IntentState
, 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. - When writing a match expression against
MergeStrategy
, 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. - When writing a match expression against
MessageSelectionStrategy
, 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. - When writing a match expression against
ObfuscationSettingType
, 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. - When writing a match expression against
PromptAttempt
, 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. - When writing a match expression against
SearchOrder
, 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. - When writing a match expression against
SlotConstraint
, 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. - When writing a match expression against
SlotFilterName
, 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. - When writing a match expression against
SlotFilterOperator
, 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. - When writing a match expression against
SlotResolutionStrategy
, 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. - When writing a match expression against
SlotShape
, 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. - When writing a match expression against
SlotSortAttribute
, 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. - When writing a match expression against
SlotTypeCategory
, 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. - When writing a match expression against
SlotTypeFilterName
, 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. - When writing a match expression against
SlotTypeFilterOperator
, 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. - When writing a match expression against
SlotTypeSortAttribute
, 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. - When writing a match expression against
SlotValueResolutionStrategy
, 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. - When writing a match expression against
SortOrder
, 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. - When writing a match expression against
TestExecutionApiMode
, 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. - When writing a match expression against
TestExecutionModality
, 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. - When writing a match expression against
TestExecutionSortAttribute
, 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. - When writing a match expression against
TestExecutionStatus
, 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. - When writing a match expression against
TestResultMatchStatus
, 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. - When writing a match expression against
TestResultTypeFilter
, 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. - When writing a match expression against
TestSetDiscrepancyReportStatus
, 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. - When writing a match expression against
TestSetGenerationStatus
, 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. - When writing a match expression against
TestSetModality
, 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. - When writing a match expression against
TestSetSortAttribute
, 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. - When writing a match expression against
TestSetStatus
, 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. - When writing a match expression against
TimeDimension
, 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. - When writing a match expression against
TranscriptFormat
, 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. - When writing a match expression against
UtteranceContentType
, 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. - When writing a match expression against
VoiceEngine
, 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.