Here’s the topic explaining how to create it 
2 Likes
Hi @Lucas_Pires,
I wanted to use the Link to Screen for an onboarding sequence with 5 screens as suggested. But there is a high risk to loose a lot of work!
I had all screens set up, on each screen a Next-button with the Link to Screen action. Then I wanted to change the action on screen 4 to a compound action. Having done that, the next screen layout was lost and appeared as default! And at the same time the whole application reloaded and I couldn’t undo the change.
If you do change the action of the Next-button on e.g. the first screen, you loose all screen layouts which come thereafter! And hours of work are dumped.
Hence, I don’t know if a sequence of linked screens is a reliable solution at all.
3 Likes
As I said in the video, that was the easy way, not the safier. I’ll try to record some other ways
But if you’re in a hurry, you can take a look at this topic by @Manan_Mehta
2 Likes
Actually I have been using increment action before and turned back to it 
I started with increments but I dropped that idea as it became way too hard to manage complex ‘flows’ through an app.
I now move people through my app using buttons and custom actions, hiding the native Glide navigation with CSS tricks.
I do have people leave the app during a flow, and Glide would naturally bring people to the first visible Tab they are allowed to see. I did consider using tab visibility, but it can be nightmarish depending on how you have built your system.
In my case my app is ‘quite simple’. There is a table for CollectUser (user profiles) and one for TestFlow (conducting a corona test and everything around it). At first I was adding and deleting rows, but that is slow (5 - 15 secs?) and so horrible. I also started with GSheets … but way way too slow for my use case.
Now the system zips along. I handle navigation through the app in tabs, making it easy to build a new screen.
Today’s magic? A button on the home page so that, if the user has left the system and wants to rejoin their test flow, for whatever reason, there is an if-then-else ite-column to work out if a user is stuck… and if so, a button appears on the home screen… and I look at an ite- column in my user profiles to see which tab they are in (… because every time the user moves tab, I do Set Columns - in TestFlow - as Glide table and faster)… but I have to bring that into the User profile table (lookup) to get Glide responding speedily (I started with setting the ‘current tab’ via a relationship, but that takes 3-10 seconds to update – -too long!).
So the magic button returns you to your spot, and if you got stuck trying to do a live video, it resets things and a new agent is alerted to your call.
Fun things to do on a very quick locked-down Friday night in Berlin
2 Likes
The tab approach also makes developing in a live app easier (by controlling visibility), doing testing (routing users via buttons based on user values - toggle-testing = true kind of thing), and tracking down errors.
Yeah, right. And my mum is the Queen of England 
Very clever 
2 Likes
hahaha lol
Is there an app created or a video in a better quality ?
is there a way to make the fields “required?”
This video is a much better explanation of the concept.
