Popups: How do I close the specific popup instance inside a "On Execution" workflow?

Ask us anything How do I?
1

I have a popup where in I have created an “On Execution” workflow. I want to to trigger the “Close this popup instance” but it is not available inside the “On Execution” workflow.

image
image981×730 37.8 KB

I need the “Close this popup instance” action specifically since I want to pass data back to the workflow that opened the popup after closing.

“Close all popups” does not work here since:

  1. It will close all other instance of the popup type
  2. It does not allow passing data to the workflow that opened the popup (which is waiting for it to close to continue execution)
2

The popup components have a “Close this popup instance”. Not sure what your “On Execution” workflow is on, but you may be able to use that.

image
image954×363 21.6 KB

3

Yes, popup components do have a "Close this popup instance" node, but as I mentioned, it is not available on an “On Execution” workflow from inside the popup.

Inside my popup, I have a workflow (On Execution) that will do something then close the popup.

image
image1308×562 46.1 KB

Inside this workflow "Close this popup instance" is missing.

image
image755×525 30.3 KB

This workflow can be triggered by multiple events within the popup so I want to have a single workflow that I can trigger for all of them

4

Could you just create multiple popups and have one instance of each instead of instancing one popup multiple times? Then you can just use the “Close All Popups” node.
Otherwise, I do not think there is a native way to do exactly what you want.

5

Even if I use “Close All Popups” action, there is no option to return data ("Close this popup instance" has this).

I think you’re right there’s no native way to do it. But I think this functionality is essential. I hope they consider this as feature request.

6

Hey @CajoOffshorly :waving_hand:

Ah yes, indeed, it would be super useful. Just created the product feedback ticket.

Not sure when we’ll be able to prioritize it though. Let me check with the team is there’s a known workaround for this.

7

That’s understandable, but thanks @Joyce !

8

Hey there :waving_hand:

Quick update: unfortunately there’s no workaround at the moment.