I heard urlbox referenced on the Workflow call this morning so thought I would give it a shot and see if it could take a screenshot/PDF of a Glide screen (I also saw documents on urlbox integration. (urlbox | Glide Docs))
I used the Glide URL (https://****-demo-qtg9.glide.page/dl/0c4ad2) from the same Chrome browser I was logged in as. I got this screenshot instead of the actual screen. Do I need the integration setup and will urlbox take a screenshot of the current users Glide screen?
THX
Going to try this differently based on Robert’s video (❇️ Understanding (and hacking) Form Screens)
I am in the builder using my own login as the user but I believe Glide thinks I am looking at a screen owned by a different user. I am getting the URL from the builder. With this method when I click on the right-arrow I go to an app screen as a different user than the one I am currently logged in as. Not sure how to change this within the builder.
More experimenting.
The issue seems to be that Urlbox still needs to access your app as an actual user would. Since your app is not publicly accessible, it makes sense that their “impersonated user” can only view the login page.
Urlbox cannot fully impersonate you. Think of it as a bot that visits the URL you provide and captures a screenshot of the page. Without the proper credentials or access, it won’t be able to navigate beyond the login screen (and I haven’t used it, so I’m not sure if you can actually pass cookies in for it to impersonate).
I was trying to test it without integration and credentials. Looks like that isn’t going to work.
What is the community’s consensus on screenshots and PDFs of Glide screens and table data? This would be a user driven activity.
Here’s my take.
I will try out urlbox and let you know. Thanks Thinh.
If I recall, it was almost impossible to capture anything below the fold of the screen on a Glide app to even output to a printer. That may have been with classic apps, and I haven’t even tried since then with new apps. I think building a normal PDF process is the way to go, whether it’s something like PDFMonkey, DocsAutomator, or what I do is build a custom HTML page from the data in a web embed that contains, print, pdf, and image functionality.
