I have been working a lot with forms and custom extract/validation code to extract values. DIETs entity extraction alongside others has been very useful. However, documentation pushes “stories” a lot so I have been looking into trying to use stories to manage conversational flows instead.
The problem comes with dual entity extraction. For example, I want to use lookup and synonyms (i.e. in essence using Regex) but to get this to extract, I must give some training examples in my intents which means I always get 2 entities extracted with the same name - one for DIET, one for Regex.
On reading the documentation, do I have write some custom code to somehow get around this so I can use them in stories? Seems a lot of work when I want to use simple lookup features.
Or am I missing a trick? Just want to be sure before I start having to write custom code for stories.
Below is my simple domain extract to show what I mean:
- intent: which_car examples: | - I want to buy a car - I wanna purchase a car - Get me a [red](colour) car - I wanna buy a [blue](colour) car - I want a [rouge](colour) car - Get me an [aqua](colour) car - i want to buy a [red](colour) car - intent: colour examples: | - [blue](colour) - [red](colour) - synonym: red examples: | - rouge - synonym: blue examples: | - aqua - lookup: colour examples: | - red - blue - green
Thanks for any guidance!