Good morning hivemind!
Can one of you technical wizards tell me if it is possible to change the word “Submit” on the form container submit button to say something else like “Next Section”? Maybe some CSS trickery or something?
I’d build a custom form before resorting to CSS manipulation, but that’s me.
I considered that but here is my scenario…
I have a rather long form for our school’s yearly student registration in our app, but it is so long that trying to make edits to it is rather laggy for me. It’s also rather intimidating to users filling it out. My hope is to create a bunch of “mini” forms for each section of the registration by having an initial form screen for the first section, and then open a new screen using the submit action. This new screen will use that new row of data and have more form fields to add to that row for the next section and another “next section” button that opens another new screen with the next section. This continues until they submit it.
I agree with Jeff. Custom form.
You could still have separate sections with a custom form. Have a single row table to drive the form, and then have next buttons to change a value used to conditionally show each section. The final section would have a submit button to write all values to the main table and clear the form. All with one screen. I feel like it would be simpler to maintain in the long run, and you wouldn’t have half completed rows if a user stopped halfway through.
That’s how the original version of the registration form is set up currently. My main problem is that the data table for it uses over 400 columns between all the data fields, template columns, integration related columns, etc. This makes the glide editor for that screen miserably slow to use because there is hundreds of components being used on that screen. An example being I can edit the text in a text component and it might take 10-15 seconds for it to actually appear on screen and sometimes the browser even asks if I want to close the window. It’s not even an issue with how powerful my computer is since I have a fairly beefy computer that handles just about anything with no problem, but the editor for that specific screen is horrendous to use. That’s the main reason why I wanted to break it into multiple screens so I only have a couple dozen components on each screen.
Do you think it’s a problem with the number of table columns, or the number of components? I’m assuming your proposed solution would still use the 400 column table?
You could do a hybrid of both ideas. Still use a custom form, but then have each section open a new screen pointing to the same helper table row. It’s not far off from what you are proposing, but scraps the native form which does give you control over the submit button.
The problem I have with CSS manipulations is that it’s injecting CSS overrides on top of existing CSS. Just feels like a hacky override to me. Don’t get me wrong, I do use CSS when necessary where glide falls short, but I use it sparingly.
I think I’ll go that route. I think the large table still plays into the problem a bit, but not near as much as the number of components.