Help with Modal UI Logic and Selections

[jarh15]

Hi all,

I'm trying to build a user experience with modals where a user makes selections in two steps. I need help figuring out the best way to structure this interaction using Workato. Here's what I'm trying to achieve:

Step 1: First Modal – Choose Outcomes 

The first modal should present 6 outcome options. The user can select up to 3 of them. It should look like this:

Example selection: User picks Outcome 1, Outcome 4, and Outcome 5.

Step 2: Second Modal 

After the first modal, a second modal should open. This one displays the selected outcomes from step 1, and for each of them, a list of associated use cases (max 3 selectable per outcome).

So if the user selected Outcome 1, Outcome 4, Outcome 5

The second modal should look like this image:

[1dheeraj2]

Hi @jarh15 , they can just type "all" and all use case will come in drop down in second modal.  You can also go for checkbox and static type of list that comes without typing anything. In that case, you need to write a python script.
In the dynamic menu recipe, use collection sql and put a condition like this

[jarh15]

Thank you! Do you mind sharing the python solution if you have it?

[1dheeraj2]

Have a look at this reicpe.

https://app.workato.com/recipes/58548439?st=2ad38a78527481fb87a4ebd780b56f54c08390c8ad1aa7063d2bb197...

used a lookup table for outcome and use case relationship.

---

Please note: You will receive your modal and be able to submit the use case by selecting it. However, to capture the submitted values, you will need to create a separate recipe with a view_submission trigger.

[jarh15]

This is absolutely amazing! Thank you so much, this is exactly what I need. I'm just having trouble configuring the custom action in Slack. How does it need to be configured? It is asked for a method of the request. Also, for the separate recipe, how does that need to be configured other than the view submission event? Apologies for the ignorance here. 

[1dheeraj2]

You can configure your custom action as shown in the screenshot.

For the view_submission trigger, you will get your selected response in the trigger itself. You will need to use functions to extract the selected use cases and execute the next actions.