Thanks so much for sharing your form, LaurenRos. Weâve already started using forms too.
Weâve tested almost everything from the âtodayâs feature setâ listed above, but honestly, thereâs always something new to discover.
Your form looks fantastic and the content is great. I absolutely love the icon idea. The tree-planting idea is such a nice bonus. I also had no idea you could edit the link name like that, super clever!
I donât want to just copy it, but would you be open to sharing your setup?
Great job guys
When are the phone, address(location), email and number fields going to be available? These are the only missing field types preventing me from using the built in forms.
Forms feel great already. Clean UI, smooth UX. Excited for conditional logic and big thanks to the team! @LaurenRos weâd also be very interested in using your form if youâre open to it.
Hey @Luis â we absolutely love your idea of multi-page forms!
We believe this could improve many use cases. Our vision is to support multi-page functionality both in forms and in the new record.
@buildingwealth â youâre absolutely right! All of those fields are super important.
Weâre working on features like the Files field and more (see âComing Nextâ above).
Huge thanks as well for the feedback in this weekâs survey. Weâll make sure the results are reflected in our feature roadmap. Honestly, because of all that, we canât share an exact release date yet, but those fields are on our roadmap, and weâre excited to get them to you as soon as possible so you can make full use of the new form experience. In the meantime, just an idea:
You could use a single text field in your form for each value you want to collect, for example, one for email and one for phone.
In the linked database app, where the records from the responses are created, you could use an automation to copy those values from the single text fields into the correct field types you need.
Of course, this doesnât replace proper field types like email or phone, but it might help as a temporary workaround until all fields are available in forms.
@LaurenRos - thank you for sharing the great, beautiful form! Category dropdowns are on our list, thanks for highlighting that, super helpful!
Thanks again for all your amazing input, we truly appreciate it.
Thereâs a lot of exciting stuff ahead.
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.
).