Reusable sub-flows callable as "functions" in a programming language.

Completed

VAN VOSSEL Dominik (ITS/DCI)

October 01, 2019 08:02

We have sometimes reusable mini-flows (often of a technical nature to handle some back-end integration which requires pre and post processing).  These mini-flows are "invoked" at different points in normal, functional conversational flows.

Currently, when such a mini-flow is called we have to implement our own "back" logic.  Meaning, prior to calling a mini-flow a session variable (eg. back) has to be set with a simple string value.  The final step of the mini-flow is then an if-then-elseif-elseif-...-else structure testing each possible value of the back session variable in order to "GoTo" (jump back) to the point in the conversational flow where the mini-flow was initially invoked.

It would be easier when such a "back" feature was natively present in some form.

1

• Official comment

  

  Joachim Jonkers

  February 06, 2020 16:50

  Good news, we have released functionality that can be used to cover the use case you describe above. You can find the documentation here.
• 

  Miguel Moreno

  October 25, 2019 13:13

  Dominik,

  in fact we also would be interested in this kind of feature.

  Maybe a simple parameter named 'nextStep' of type DialogState could help to be reused in the last step of the called mini-flow to route to.

  I haven't figured out how to pass a dialogstate ref to another dialog, like you can do when calling an API.

  0

Please sign in to leave a comment.