Just to add some more into it, I also thought about having some kind of reference of the process (like a progress bar, some page numbers, or something similar).
Then also, some conditional next page depending on filled fields but this of course is going to depend on conditional logic itself (and its implementation). I mean having the ability to have two completely different second pages depending on the filled fields on page one.
Finally, it could be interesting to think about the progress from page to page (require manual action or automatically when filled), if there are restrictions (required fields on page one to continue to page two) and also if this is a vertical move (like a “sections” effect) or a horizontal one (more classic page to page).
Hi @Leo,
Wow! This multi page feature applied to records would be soooooooooo valuable. It would allow to better assign space and so much more to better organize everything.
Screen real estate is a bit hot and pricey nowadays with the current record implementation.
I loved the option to turn table into a form. But this showed me a situation, which I never had before - just because we always needed to have a form and a table separately
Look at this situation. Its a recruiting app. I ask the applicant how he found us. In the past I filled out this field. Now I can ask the user itself. But the option I want to show my applicants are less than the ones I want to be able to fill out. So I thought about removing one or more options from that question - still keeping the field connected, but to have more options in Tape itself. Currently I could only kill the option completely - thus also loosing the existing data. Basically internal and form view need to be in sync in terms of available fields.
I know, its a wish that comes up because its so well integrated. Its not a bug, its maybe some v2 idea. So while people can make some selections in the form, I could add more options inside - because the same application may be fed by another channel.
(maybe an answer in a question just needs the option to be hidden)
Thanks a lot for your super insightful feedback! Really appreciated
We actually came across this exact situation while designing Forms and Layouts. That’s one of the key reasons we introduced Rules as a general solution for these kinds of problems.
With Rules, you’ll be able to show or hide specific category options (and later also members, relations, etc.) – even without a condition. This means you could keep all your internal options, but only show a smaller selection in the form for applicants. That way, your internal setup and the form don’t have to be 100% identical anymore.
In fact, the exact kind of rule you’re describing already exists in our planned rule action list: “Hide options” or “Show options”. It’s fully built into the concept and will definitely be part of a future release. So yes, it’s coming!
Hi @dirk_s,
I came across a similar problem the very first day I started using Tape forms. You probably already know about this but just in case let me tell you the workaround I found.
I created another app and form cloning and deleting the options that aren’t needed. I then connected the submission with the original one using automations on submission/record creation.
I know it is quite clunky/painful, could add noise (specially for search or messing apps), and depending on the case could not be a solution (it is not dynamically hiding/showing fields)…
hidden field for JavaScript to read e.g. referring URL or read a variable from the URL (e.g. to use one application form for a variety of job posts, but to automatically identifying the referring one),
allow to change the wording of the submit button, (e.g. apply, order etc.)
(I bet other field types like email and phone will follow anyway ).
thanks a lot for the report! It might indeed be an issue with the feature flags. We should definitely double-check that for all users to be safe.
Could you please send me the email address of the user where this happens via Direct Message here in the Community, so we can make sure we’re checking the correct account?
thanks a lot for reaching out
At the moment, our full focus is on developing the relation field, including all connected features, which is a pretty big and important building block for us. Once that is done, we’ll take another look at the roadmap and see when a redirect after submission could fit in.
However, we’ll also do a quick check on the effort required and see if there’s any chance to squeeze it in earlier. I’ll definitely keep you posted if we see an opportunity for a sooner release.
It’s been years, and I’ve said it multiple times, but it’s still so refreshing to work with a partner as transparent and honest as you and the rest of the Tape team.
No waitlist anymore.
Just select “Form” when creating a new app in your workspace.
As always, we truly love hearing your feedback.
To keep things organized and moving fast, please post your feedback here: Feature requests Issues & bugs
Amazing! Almost there!
Numbers next? I’m guessing a form where someone is able to put in number-hours, number-money, number-quantity is quite useful. I can’t move to Tape before the feature is there ◡̈ How far away are we? All the best!
great to hear that this is the last missing piece for you to make the move over to Tape, that’s amazing news
We’re almost there: it’s a matter of days, not weeks. We’re planning to roll out the number field next week.
Looking forward to having you on board!
).
relation field for forms 