# Best Practice for Show Detail Screen/Edit screen/Form **URL:** \ **Category:** General\ **Created:** [January 10, 2025, 4:30pm UTC](https://community.glideapps.com/t/best-practice-for-show-detail-screen-edit-screen-form/79118 "2025-01-10T16:30:40Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![MattLB](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mattlb/32/41284_2.png) [@MattLB](https://community.glideapps.com/u/MattLB)\ **Post date:** [January 10, 2025, 4:30pm UTC](https://community.glideapps.com/t/best-practice-for-show-detail-screen-edit-screen-form/79118/1 "2025-01-10T16:30:40Z")
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? Thoughts?? ---
**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\ **Post date:** [January 10, 2025, 4:45pm UTC](https://community.glideapps.com/t/best-practice-for-show-detail-screen-edit-screen-form/79118/2 "2025-01-10T16:45:42Z")
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. ---
**Author:** ![MattLB](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mattlb/32/41284_2.png) [@MattLB](https://community.glideapps.com/u/MattLB)\ **Post date:** [January 10, 2025, 5:27pm UTC](https://community.glideapps.com/t/best-practice-for-show-detail-screen-edit-screen-form/79118/3 "2025-01-10T17:27:40Z")
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 ---
**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\ **Post date:** [January 10, 2025, 5:47pm UTC](https://community.glideapps.com/t/best-practice-for-show-detail-screen-edit-screen-form/79118/4 "2025-01-10T17:47:34Z")
Good idea. I can’t imagine there would be a lot of overhead, if any. ---
**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\ **Post date:** [January 10, 2025, 9:28pm UTC](https://community.glideapps.com/t/best-practice-for-show-detail-screen-edit-screen-form/79118/5 "2025-01-10T21:28:00Z")
> [@MattLB](#): > > 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? 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. ---
**Author:** ![Robert\_Petitto](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/robert_petitto/32/25193_2.png) [@Robert\_Petitto](https://community.glideapps.com/u/Robert_Petitto)\ **Post date:** [January 10, 2025, 10:24pm UTC](https://community.glideapps.com/t/best-practice-for-show-detail-screen-edit-screen-form/79118/6 "2025-01-10T22:24:30Z")
> [@Darren\_Murphy](#): > > Everything else is a named workflow - religiously. Agreed. The only time I set action directly is Show Detail Screen or Show Edit Screen. Everything else (New Screen, Form Screen, etc) is a workflow.