We have a issue with this widget when the user navigates away and opens a new screen because the microflow and popup is not stopped. So after you navigate away and the data is finily retrieved you suddenly end up in just the popup. There should be some mechanisme to detect this so the popup is no longer triggered.
Non responsie UI is not helping, sometimes giving user feedback will make your app much better, even if they need to wait. I wrote a smal blog about it https://www.mansystems.com/mendix-progress-button-indication/
Good to know this is out there.
Just out of curiosity, I don't think the postCreate needs to call the _updateRendering() or _setupEvents()? Because the update function is called right away anyways, and the setupEvents function doesn't do anything.
Also question? How does this widget handle the microflow execution? It doesn't poll correct? It just calls the microflows async, and triggers the refresh at the end of the microflow? So no matter how long the microflow takes it will not refire it? Thinking whether it would be useful to allow for setting a time-out in this widget or whether that should just be handled by a timer inside the microflow.
Anyways looks like a nice widget.
Do not use this widget in combination with the ShowByCondition widget. The datasource microflow for some reason never gets triggered.