Finally you can create Form Views in Fibery and capture data from random people all over the world! Check the blog post with more details and give us feedback to improve Form View in the next releases. Forms were in experimental mode, in this release we’ve added:
Default values for fields
Hidden fields (so you can set default values and setup some automations on top)
My top five, scratch that, six next requests (for now, possibly posted in the wrong place, probably already on a list, and in order):
Filter relation drop downs based on a formula or filter (ex. don’t show events in the drop down that are in the past (Done) based on the Workflow status or date. For my use case, it would be very helpful to narrow the list down to one event type and status.
Conditional logic for hiding/filling fields (do you ever foresee adding multiple pages to a form? I only have a couple use cases but am curious.)
Now that it is more public facing, the need for week start on Sunday and 12-hour time is greater where I live.
Payment integration (Stripe for me)
Different embed codes in Share button
Thank you for prioritizing this feature as it will greatly reduce integration/entry time and move all of us one more step to using Fibery for everything we possibly can.
I both love and hate it. It can be challenging to maintain, so always looking for ways to reduce it, but it really does make certain forms function in a unique way that allows a needed process to occur based on responses. I will think on this more and other ways to handle it with Fibery forms.
We currently have quite a few forms that collect payments for events, classes, and donations. Having the payment directly tied to the entity is a nice feature versus redirecting to a payment site or some other method. I’m certain this is a larger feature to implement, especially with the amount of payment gateways that exist, but doing the top 2 or 3 would be nice.
That works great. Custom CSS isn’t a need, just a nicety to make embedded forms match the website style.
We’ll move now all HR related stuff to Fibery. We used Breezy before, but with this, we don’t need it anymore… maybe embedding documents inside websites would be great to have so we can embed the content of the JD and style based on our brand.
I am super excited about forms! This is a fantastic release. Below are my dream items for forms, but already this is awesome.
Form view inside of smart folders (with the smart folder level becoming an auto-defaulted hidden field on the form)
Filter relation control (very excited for ‘Filter and sort in relation field selector’ roadmap item)
Conditional hidden logic
→ Allows one form with a lot of functions for a single database rather than a lot of specific forms.
→ My immediate use case: lessons learned database. One of the reasons I am sold on Fibery is because I can design a system that connects relevant lessons and key information to a user based on their current needs. Forms offers a way to add in items that can’t be captured by normal Fibery use. But capturing that knowledge should be as frictionless as possible. Being able to select a choice from a single-select (“what kind of lesson are you submitting?”) and then having the relevant fields appear would be very useful. Without this, there are fields that ideally should be required or hidden but might be applicable in some scenarios.
Within relation dropdowns, ability to customize fields shown within the relation picker
Customizing the ‘Thank you for submitting’ page
→ Loop button to submit again
→ Rich-text fields where you can add a transclusion of a view. This is useful for feedback of the submission and seeing what other items should be submitted. An alternate approach to this would be the ability to launch a form view from a button and then return to the view/entity after submitting
Customizing the banner and adding an option for the workspace logo as the icon
This please, it still trips me up after 1… 2? years of using Fibery.
Yeah this was not obvious at all and I thought it was a odd design decision to make forms public focused - to the point where I started creating documentation linking to the public form page for internal use.