I am going through all my screens to find any direct actions (instead of Workflows) in my Apps because of the Set Column Value issue within Collections.
I found one Set Column Value but many Show Detail Screen which leads to my question.
Is it best practice to encapsulate Show Detail Screen (or Form or Edit) within a Workflow so you see all the uses and other details Glide creates for builders? For example, this way I can find all usage of Show Detail Screen before I make any future changes to the screen?
It’s probably up to personal preference. I typically just set an action directly, and if I need to reuse it or add additional actions, then I’ll convert it to a workflow. It’s worked out fine for me. I keep that Undo button on reserve if something ever gets messed up.
The only exception for me might be if I have an action that goes to a new screen that has several layers and actions beneath it. Those are ones you probably want to get into workflows so you don’t risk losing a large portion of you app by changing something at a top level. A simple action like Show Detail Screen is usually pretty safe though because the detail screen layout will be linked to it’s source table.
Previously I encapsulated all Show New Screens into Workflows so I have a full counting/list of all my Screens. I am converting the Detail Screens into this method so I can use the ‘Usage’ feature Glide now supports for Workflows.
Is their a performance or some other overhead associated with putting direct actions into Workflows? I really like the accountability
About the only time I’ll ever configure an action directly in the side panel is for something insignificant such as a Close Overlay on a Cancel button. And even sometimes then I’ll make it a workflow. Everything else is a named workflow - religiously.
