I’m looking for some best practice advice on onboarding please.
My first screen collects some user data and creates a row in User Profile table, as normal.
In my second screen I’m using 5 form containers with multiple data entry fields, text entry, date, choice etc (same in each container but linked to different activities progressively, Activity_1, Activity_2 etc).
I have a button (Add Activity) which should reveal container one to complete and submit, then container 2 if container one is complete and so on. I’m using visibility logic options to manage this.
My problem is that the second screen is creating a new Row with each container submission.
Is there a specific way the first screen should be linked to the second? Is there “best practice” for using multiple containers in a screen for progressive onboarding?
I’ve created far more complex functionality in the app but I’m really stuck on this.
Forms add rows. Every time you click submit on a form or a form container, it will add a row. The purpose of forms are to add rows. They are not meant to edit existing rows.
If you want to edit an existing row, then you either need to use an Edit Screen, or just show a detail screen and edit the values in real time.
Thanks Jeff. I’ve switched to custom screen with components. I had thought form containers would give me an efficient way to group items the reveal progressively for user data submissions.
I’ll use visibility conditions to reveal groups of components to users as they complete preceding ones and progress through onboarding.
I also made the mistake of creating individual onboarding screens with the plan to link them up. I now realise that a workflow needs to be created at the end of each screen to create the next screen in the sequence. Even then, editing each screen requires going through from screen one to reveal screen to be edited. I’m trying to find an elegant way to do multi step onboarding with progressive component reveal..
Another option is to use one screen with several containers and your components in each container, and then have a button that sets a value in the table to control which container is visible.
Yep! I just realised that I’d been using Form Containers to do a containers job! Thank you…It’s really going to help with the visibility / progression stuff.