Enable custom slot validation for multi-turn dialogs when using manual delegation to provide a default.
The use case is described in the docs here: https://developer.amazon.com/docs/custom-skills/delegate-dialog-to-alexa.html#default-value-example
The exception being that I'm using a custom slot with validation (entity resolution). If I send a response back with Dialog.Delegate and include the entity resolution in that response, it's ignored by the Alexa service.
A more complete description of the issue with example code can be found here: https://github.com/alexa/alexa-skills-kit-sdk-for-python/issues/85
Yes, please fix this issue lot of testing and now I discover is a bug happening to many other mates.
Validations do weird behavior when addDelegateDirective is used and we set a slot with a valid value, but alexa still launch the validation.
Thanks in advamce!
Would really appreciate a fix here, we have a lot with validation to only allow slot name and synonyms but we can't use addDelegateDirective because it asks the user again to specify the slots even though the ones we have set are valid
Andrew Sephton commented
Voted! This functionality is counter intuitive.
In my scenario the user has provided the slots and I they are iterating over a list of items by voice.
Using the dialoge.delegate for this with the slot values pre-populated should simply run the intent as all information is provided and valid.
Instead the user is always asked to provide the slot values again, which is a poor experience.
Does anyone have a workaround for this?
Ashish Jha commented
This issue is also observed here - https://github.com/alexa/alexa-skills-kit-sdk-for-nodejs/issues/539