With our upcoming UI update, we've moved some furniture around, but we also took a couple of pieces to Goodwill. This FAQ will help to explain why.
What is changing?
The form builder gadget configuration panel is getting a refresh/overhaul. It will make modifying your gadgets easier and clearer. But the change also involves removing some features that people are using now.
Wait, you've removed features? Which ones?
The ability to hide the gadget label
The reason for this is that right now, it creates a disparity between what is in the workflow and what appears in the form. Take the following example: User #1 is referencing a gadget in a workflow and the label for that gadget is hidden. Person #2 comes in and sees the reference and goes to the form to make a change. Person #2 can't find the gadget in question on the form. This makes it look like things are broken, especially for new users. It's also best practices in forms for there always to be a label on a field. The ability to hide a section header will remain, however.
Field Long Label
This configuration option has been very confusing for new users and was originally created as a kind of band-aid because we were thin on some other features (namely the custom column option). With the addition of the custom column (see below), and the Help/Description option still being intact, this option becomes less relevant.
What is being added?
Custom Column Name
This configuration option has been needed for a long time. It makes it possible to set a short column name for this gadget in the Document List. So if you have a label on a gadget that is very long and would make the document list really stretchy, this setting will help with that.
What happens to my old forms/data?
All forms will eventually be upgraded to the new UI. Any old data will also be migrated. We will be working one-on-one with each school to determine the best migration strategy for you.
Couldn't you guys just leave my old forms the way they are?
Yes, but here's why we all don't ultimately want that: Keeping data around when the structure of the data has changed has the effect over time of making an app more complex and unstable. This hurts the user experience in a bigger way than if we ask folks to do a small data migration now. We will try, however, to keep changes like this to a minimum in the future.
Thanks for your patience with us.