addressalign-toparrow-leftarrow-leftarrow-right-10x10arrow-rightbackbellblockcalendarcameraccwcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscontroller-playcredit-cardcrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobe--smallglobegmailgooglegroupshelp-with-circleimageimagesinstagramFill 1languagelaunch-new-window--smalllight-bulblightning-boltlinklocation-pinlockm-swarmSearchmailmediummessagesminusmobilemoremuplabelShape 3 + Rectangle 1ShapeoutlookpersonJoin Group on CardStartprice-ribbonprintShapeShapeShapeShapeImported LayersImported LayersImported Layersshieldstar-shapestartickettrashtriangle-downtriangle-uptwitteruserwarningyahooyoutube

Re: [ia-55] Required and optional fields

From: Christian S.
Sent on: Tuesday, August 17, 2010, 8:50 PM
I like the approach of getting rid of the optional fields all together. Cause after all, who WANTS to give more information. But after you've pushed and the business won't let go of their beloved Salutation field, I would use the asterisk on required fields. I definitely see the point of making the low number standout, but users are used to asterisk = required.

I'm still undecided on the tinted fields. It's probably just my background, but it tends to highlight the fields that should not be there to begin with. And now you have an extra layer of visual clutter and information for users to decipher.

Christian


On Aug 17, 2010, at 6:09 PM, Mary Anderson wrote:

LOL. I use the red asterisk all the time.  Sometimes, though, my clients tell me that red equates to anger for them.  I had to choke back laughter the first time, but have since learned to keep a straight face.  Every once and awhile the red asterisk doesn't go with the client's color scheme, so I have to change it up a bit.
 

Mary J. Anderson

Integrated Management Processes

[masked]

20296 E. Arrow Highway, C

Covina, CA, 91724

Asset Leveraging Leader and Executive Coach

[address removed]



From: Ben Saine <[address removed]>
To: [address removed]
Sent: Tue, August 17,[masked]:48:17 PM
Subject: Re: [ia-55] Required and optional fields

What happened to the red asterisk?




-----Original Message-----
From: Eduardo Favio Angeles <[address removed]>
To: [address removed]
Sent: Tue, Aug 17,[masked]:58 pm
Subject: Re: [ia-55] Required and optional fields

I would recommend you keep it consistent throughout the application and rule of thumb is that you make the required fields stand out as those are the important fields needed. 
You can try shading the required txt fields with some light color (which one depends on your color palette) on a white form we usually make the required text controls khaki or pale yellow, and we also have client side required field checkups, usually a regex).

Sounds like is a lot of forms... You can also consider having something like an application metadata layer and have the forms programmatically driven from the metadata, and you simply need to craft a CSS to make it all nice...  

Fun project!
Sent from my iPhone

On Aug 17, 2010, at 1:57 PM, Suman Bhaskara <[address removed]> wrote:

Hi all!

How do you best represent required and optional fields in a form-based application.
This is a backoffice application with lists, reports, various forms (short and lengthy)

When a define a blank slate for a form, if a form has few optional fields, I'd mark them as inline-field text. It is understood that rest of the fields which are empty are required fields.
Alternatively, if most fields are optional, I'd mark only those that are required.
I would use one of the pattern for the entire website or application

But what pattern would you follow in a large application (about 250 unique screens) which has both of above patterns?

Thanks ahead
Suman




--
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
This message was sent by Suman Bhaskara ([address removed]) from The Los Angeles User Experience Meetup.
To learn more about Suman Bhaskara, visit his/her member profile
To unsubscribe or to update your mailing list settings, click here

Meetup, PO Box 4668 #37895 New York, New York[masked] | [address removed]




--
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
This message was sent by Eduardo Favio Angeles ([address removed]) from The Los Angeles User Experience Meetup.
To learn more about Eduardo Favio Angeles, visit his/her member profile
To unsubscribe or to update your mailing list settings, click here

Meetup, PO Box 4668 #37895 New York, New York[masked] | [address removed]




--
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
This message was sent by Ben Saine ([address removed]) from The Los Angeles User Experience Meetup.
To learn more about Ben Saine, visit his/her member profile
To unsubscribe or to update your mailing list settings, click here

Meetup, PO Box 4668 #37895 New York, New York[masked] | [address removed]





--
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
This message was sent by Mary Anderson ([address removed]) from The Los Angeles User Experience Meetup.
To learn more about Mary Anderson, visit his/her member profile
To unsubscribe or to update your mailing list settings, click here

Meetup, PO Box 4668 #37895 New York, New York[masked] | [address removed]

Los Angeles, CA

Founded Apr 21, 2007

Organizers:

Eagle, PIT, Star and 2 more…
Contact

People in this
group are also in: