Good news - I can find the Layout Screen where a Workflow is called from.
Bad news - where did this Layout Screen get called from? How is this Layout Screen accessed from the App.
Is this knowable either within Glide editor or as a best practice?
Net/Net: from where in the App (via an interaction) is a Screen called from?
TIA
PS…Probably overlooking something really obvious!
As far as I know you don’t get that kind of information. You have to try adding breadcrumbs to the screen perhaps, to see if it shows the navigation to get there.
Though if you navigate to the screen through a “Find Uses” feature then it might not be useful.
Yeap, same problem here. I have lots of extra screens I m never using, or they are just existing yet not accesible only with “find uses” and it uses memory, slowing down the app for no reason and can’t get rid of them. There would be nice if we had something to control each screen, or like a data with all the screens we have ( and source )
We don’t have any concrete evidence that having those screens actually use your memory though. In most cases, optimizing your computed columns/images is the most straightforward way to make your app faster.
I agree with Thinh.
In fact, anytime a new table is created, one could say that the details, edit and form screens exist by default. The question is then whether they are called or not via an action in the layout.
New screens are different. It would be nice if we had a flow chart of screens of the app to see all existing and active screens, and ideal how they link together. But this is a separate discussion I think.
I would assume that screens that are not called by the app are considered inactive by the system and would therefore not require any resources. This is only an assumption.