I have an requirement where more than 200 fields should be there in the Form. Please suggest which approach will be good to proceed with.
If your CDT is hundreds of fields, that's a very bad approach that you will definitely need to correct.
You could look into various different improvements to the form to increase its readability. The great thing is that you can do multiples of these at the same time, mix and match how you see fit.
Breadcrumbs, Tabs, Wizards, others have discussed. You can also use a milestone component to achieve the same effect. Especially with clickable milestones that allow you to return to previous sections of the form. It might seem old and trite, but Appian recently gave it an extra design option with the vertical milestone. These are all useful, maybe not all at once, for when you want to break the form up into larger chunks that clearly don't need to be filled out at the same time. You ideally don't want more than 7 of these, so you're still looking at about 30 to 35 fields per milestone/tab/breadcrumb.
30 to 35 can still be way too much for a human to process all at once.
Now, INSIDE each large chunk, what can we do to break it down further? We can use columns to separate some fields and condense the whole form to avoid scrolling. That tends to confuse some users which fields are associated with which fields. We can use Box Layouts or Card layouts to organize fields further. That's especially helpful for putting a few fields in one column and demonstrating that they're separate from the fields on the next column. For instance, if billing address were on column 1, and shipping address were on column 2, you could put those in box layouts to visually separate them and prevent users from mixing up addresses. You could also add a check box to the bottom, in that example, so the user only has to fill out one of them and auto-populate the other.
Do you have fields that aren't mandatory in some situations, but are in others? Do you have some that are disabled in certain cases and can only be used in certain other cases? You can eliminate those completely from many users' experience by using progressive disclosure. You use the showWhen input to hide them rather than disabled to keep them visible and taking up space. Have an entire group of related fields that don't necessarily need to be filled out? Put them all in the same collapsible Section Layout.
You can even use progressive disclosure to hide entire collapsible sections until each of the required fields in the section you're displaying has a valid value, then collapse that section and open the next. Even without using the collapsibility, you still shouldn't overlook the benefit you can get just using Sections to break up the visual clutter. They say humans can focus well on between 5 to 7 things. If you can visually group your 200 fields into groups of 5 to 7, even with just barely enough to allow the user to tune out the rest, you'll have a much better form.
Additionally, I would also add LOTS of controls users can activate to save their work all over that thing. No one wants to put in 199 values, get called to a meeting, find out they got timed out when they get back, and have to start over from the beginning. If you make it so that person in this nightmare situation gets to keep 180 of the 199, they will love you forever!
Discussion posts and replies are publicly visible
© 2020 Appian. All rights reserved.