What's New in Alexa Conversations
Since the public beta launch of Alexa Conversations, we've made the following improvements.
- Updated the functionality of the
shouldEndSessionflag. For Alexa Conversations skills, the functionality of the
shouldEndSessionflag is now the same as with other custom skills, as described in Request and Response JSON Reference. Prior to this update, Alexa Conversations skills that didn't set the
shouldEndSessionvalue would, by default, have the
shouldEndSessionvalue set to
March 1, 2021
- Went General Availability (GA).
- Added support for Alexa entities for
February 18, 2021
- The command-line experience, Alexa Conversations Description Language, went public beta.
November 30, 2020
- Added user interface validations and error messages that notify you of the following:
- Undefined variables.
- The Affirm/Deny dialog acts must follow the Confirm API/Confirm Args dialog acts.
- The Inform Args dialog act must follow the Request Args dialog act.
- Dialogs must start with a user turn that uses the Invoke APIs dialog act.
- Dialogs must end with an Alexa turn.
- Dialogs must alternate between user turns and Alexa turns, except when an Offer Next API dialog act follows an API Success/Failure dialog act.
- If more than one argument is requested for the Request Args dialog act, the Alternate Responses section contains a line for each required API argument. You can't modify these arguments or delete these lines.
- User input validations.
- Prevented you from using the same slot name multiple times in a sample utterance.
- Made dropdown names visible on hover.
- Disabled the Evaluate Model button when Alexa Conversations is the default dialog manager.
- Added comments on the Analytics page to indicate how Alexa Conversations metrics are reflected.
- Added a pop-up warning message before overwriting changes made from a separate tab.
- Added Alexa Conversations skill responses in the Alexa app.
- Automatically updated dialog turns with the Request Args and Confirm APIs dialog acts when changing mandatory API arguments.
- Added hints on how to create dialogs in the right fly-out.
- Made the following improvements when you configure responses:
- Removed the + button. To create a new line, you now use the Add prompt button or press enter.
- Removed the Create Prompt, Create and Edit APL Audio, and Reset buttons. Instead, you name your APLA document and enter Alexa prompts. The APLA documents are saved when you save your skill. You can still navigate to the APLA editor tool by clicking the APL for Audio editor link in the notification banner.
- Removed the + button when you configure user utterance sets. To add a sample utterance, you now click the Add Utterance button or press enter.
- Resolved data loss issue caused by editing the same skill in multiple tabs.
- Added documentation to explain how to troubleshoot and resolve the most common validation messages: MissingRequestTemplateV2, MissingDialogAnnotation, MismatchArgumentSize, and MissingSampleUtterance.
- Reduced friction around multiple save buttons on the response page and added clearer call to actions in the developer console.
- Enabled developers from outside the US to test their
en-USAlexa Conversations skills.
- Enabled slot types with values, which you can use to represent strings in API definitions and responses, without requiring dummy values.
- Reduced friction in authoring responses in the dialog annotation flow by automatically filling in default response and prompt names.
- Resolved the issue where dialogs were not automatically updated when utterance sets, responses, and API definitions were updated from the left navigation.
- Added new validation messages to fast-fail the model build and advise how to resolve issues such as the following:
- An utterance set has a null slot type
- There are slot types (with properties) without defined properties
- There are inconsistencies between arguments in API definitions and dialogs
- The argument name of the API must match the arguments of the dialog acts
- Improved model build error messages to advise how to resolve issues such as the following:
- The first user utterance in a dialog is missing
- Annotated dialogs are not yet generated
- An utterance set has an argument that contains special characters
- A dialog is missing annotations
- An API definition is missing
- Provided minor user experience upgrades such as the following:
- Improved Firefox support
- Added support for pressing enter on any dialog turn to create new, blank user and Alexa utterances
- Added inline warning messages when slots are not set
- Renamed response condition to API success condition / API failure condition
- Highlighted the link to known issues on the dialog page
- Restricted a single list slot per annotated utterance
- Prevented the right fly-out when annotating slots and clicking outside utterances
- Fixed the pagination bug
- Added dialog cloning capability to enable you to create similar dialogs faster.
- Added autocomplete of response names in the left navigation, utterance sets, and API definitions to reduce the effort required to create new components.
- Added automatic propagation of changes to annotated variable names and API return variable names across the dialog to reduce the effort required to manually update them.
- Enabled you to create all required Alexa Conversations components as you annotate dialogs so that you don't have to leave the dialog annotation flow and click separate tabs to create the required components. Specifically, we:
- Removed the requirement to provide API definitions in utterance sets
- Removed the requirement to provide API definitions in responses
- Enabled you to create, edit, and delete API definitions from the right fly-out during dialog annotation