When you're creating a dialog for slack the recipe terminates after the dialog has been posted. I understand why but this doesn't work well when if you're trying to keep track of more than 5 "fields".
If I want to hold data sets, I have to use one of the 5 fields to put in an ID that is connected to a Workato Lookup table that can be called in the recipe that is called when the dialog is submitted.
Ideally, we'd have an option to "wait for submit" to keep the recipe "alive". When the user submits the dialog the original recipe where the dialog was posted continues to run with the outputs of whatever the user submitted. You could even add a timeout option that will only wait max 5,10,15 minutes for the dialog to be submitted before the recipe errors out.
Additionally, because we only get 5 fields (4 really, if we're keeping track of a UID) then I have to create many recipes to collect the data that I need.
Chase Friedman
Slack Dialog - stay within the recipe
When you're creating a dialog for slack the recipe terminates after the dialog has been posted. I understand why but this doesn't work well when if you're trying to keep track of more than 5 "fields".
If I want to hold data sets, I have to use one of the 5 fields to put in an ID that is connected to a Workato Lookup table that can be called in the recipe that is called when the dialog is submitted.
Ideally, we'd have an option to "wait for submit" to keep the recipe "alive". When the user submits the dialog the original recipe where the dialog was posted continues to run with the outputs of whatever the user submitted. You could even add a timeout option that will only wait max 5,10,15 minutes for the dialog to be submitted before the recipe errors out.
Additionally, because we only get 5 fields (4 really, if we're keeping track of a UID) then I have to create many recipes to collect the data that I need.