Can the routes taken by the bot to trigger tasks be constrained?
For example, say I have a menu task; which lists all of the bot's functionalities. I want all of those tasks to only be triggered from that menu action, kinda like a finite state machine; where states can only be triggered by another given state. Currently I'm using the listen action with the tasks sub-property; but still, there are actions that trigger when they're not suppose to.
We're a place where coders share, stay up-to-date and grow their careers.
Hey Dominik, I have another question for you 😅
Can the routes taken by the bot to trigger tasks be constrained?
For example, say I have a
menutask; which lists all of the bot's functionalities. I want all of those tasks to only be triggered from thatmenuaction, kinda like a finite state machine; where states can only be triggered by another given state. Currently I'm using thelistenaction with thetaskssub-property; but still, there are actions that trigger when they're not suppose to.