Has anyone found a way conditionally halt an “execute all” and open a component’s interactive view? I can conditionally stop downstream execution, but I would really like the workflow to auto open the interactive view where the necessary changes / corrections will be made.
Hi @iCFO,
You can select all nodes and do execute/open view:
And as you mentioned you know how to stop the execution by a condition.
I have an idea to do that but not sure if this is efficient and if it’s exactly what you would like:
1- Add a Wdiget to your components e.g., a single selection widget to select between 0 or 1 where 0 is the default value and connect it to component output. Enter the same variable name for all wdigets in all components and allow the variable in components’ input/output
2- Except for the first component, add a breakpoint node which will stop if the variable value is 0
Now, if you select all nodes and execute and open view all selected nodes (Shift+F10), the first component will execute and the view is displayed while the rest are failed. You will have an option in the composite view to select 1 which will make the next component execute and display the view when you again execute and open view all selected nodes and so on.
I hope you find this helpful. If not, please let me know what I missed so I can try to help you better.
2 Likes
That was a creative approach to a workaround, but it won’t work in a real world situation for my goals.
1 - This approach opens all of the preceding component’s interactive views, which in my case would regularly be several dozen popup windows or more…
2 - This approach really targets the components that pass the test for interactive view opening and blocks the component that has a failed test, instead of successfully executing all prior components and then executing / opening the target component before stopping the execution afterwards.
I am essentially trying to mimic a popup user entry prompt. That popup should only activate if it appears that manual changes may be required. This would allow us to build in error checks that auto open the correct user friendly adjustment settings to fix the problem. It could also ensure that a user always adjusts or reviews certain control settings before the final workflow steps are executed.
I think that an elegant solution might be a Boolean Flow Variable setting on components that controls whether the interactive view will open upon execution. That would allow us to trigger it on the first run only, all runs, conditionally, etc. This would also be pretty handy for simpler workflows that are just driving interactive view dashboards.
My hope is that it would also translate to workflows on the Hub. Serving user setting control dashboards only when necessary so that any level user can clean up data issues until they have successfully executed the complete workflow. It would even allow a popup to trigger that said something like “Database updated and all reports distributed via email” at the last execution point of a workflow.
1 Like
I see your point. I think that’s still possible by using switches and the layout settings of components (to disable views for the to-pass branch if the component itself is necessary there) but as you said, in case of too many components, it’s not very convenient.
I’ll move this topic to Feedback & Ideas and share your suggestion internally.
Thank you so much for providing us with your valuable feedback.
2 Likes
Thanks as always @armingrudd !
1 Like
Out of curiosity, you mentioned somehow disabling the views of the “to-pass branch”… How would you conditionally disable the opening of a component’s interactive view while still having it execute using workflow switches and component view layout? Are you saying that there is some component setting that keeps the interactive view from opening when Shift + F10 is executed, and you could conditionally select between the “active” interactive view component and the duplicated “inactive” interactive view version of a component via Case Switch?
Yes, there is a workaround for that. You can put the main component inside another component and in the layout settings of the parent component go to the first tab “node usage” and disable the composite view of the main component, then the parent component won’t have a composite view anymore and Shift+F10 will just execute it.
So If you have 2 copies of the same component and make one of them as I explained above, then by using the switch nodes like IF Switch, you can execute one or another where one of the branches open the view and the other just gets executed.
1 Like
Dear @iCFO,
I discussed your suggestion internally and it seems there have been thoughts around this topic but for now, there are other priorities. I will keep your idea in mind and will bring it up again in future. I also voted to the topic 
Please keep sharing your feedbacks with us. Thank you!
2 Likes
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.