I have a few plugins that collect information to fill out a ticket. The different fields to fill out are slots in the conversational process. The slots have a resolver strategy to pull the possible options from a api. I have the slots set to Infer slot value if possible. However inferring never actually works when a resolver strategy is applied.
For a access management plugin, I can say I want access to <exact application name in system> and the plugin will show the first x options. It normally ends with the correct option and says things like, if you mean <exact application name in system> type “yes” or the number in the list. It however always makes the user confirm the option instead of inferring.
I am getting around this by throwing a generate_structured_value_action at the beginning after asking for a description of the ask, but it is possible the user won’t provide enough information to determine the correct option and it feels like a hack when slots should be the answer. Is there a better way to set this up? I don’t want to just recreate a ticketing platform in text format where the bot asks for each question; it should be conversational and infer to a better extent.