What's the best way to indicate a field is required when finalizing but not when saving?

by Iben   Last Updated June 29, 2020 15:16 PM

I'm currently stuck in a bit of a UX conundrum. I need to be a bit vague about the specifics, but I hope it is clear enough.

Background info:

In our system we have certain items that need to be saved. Each item consists of multiple properties, that are grouped.

In order for our system to be able to process the item in the further stages of the system, each group has a set of fields that are required, whilst some might have fields that are optional.

Our user base consists of users that have a quite bit of computer experience but also quite a few users that almost never use a computer.

Our user base wants a draft system so they can fill in each group whenever they want; and on top of that they want to save each individual group with the info they have at that time, regardless of the fact that each field is filled in. This is because gathering said information takes time.

On top of that, we have a fine-grained permission system that allows us to prevent users from filling in group A or group B, because they are not allowed to know anything about that part of the item.

This is a extremely simplified view of what we have today

Form preview

The Case:

At a certain point in time, a user wants to finalize the item so it moves from a draft status to an item we can actually use in our system. This user has the right the finalize it, but might not have the rights to fill in each group. The user will get an indication one of the groups is missing required values, but if they don't have the rights to edit that group, they'll have to contact one of their fellow users to fill in the missing info.

The question is, how do we indicate the fields are required for finalization, but not needed to simply "save" the form?

I'm currently tasked to mark the "required for finalization" fields in an orange color once at least one field is filled in and the form has been saved at least once, like this :

enter image description here

I'm afraid this won't be clear enough to our users and this will throw them off. Except for adding a kind of legend at the top of the form telling the users what the color means, which most likely will be something they won't read, I cannot think of a way to make this more clear.

I'm a bit tied to the solution of marking things in orange, as this has been decided by the majority of the developers in our team and there's no option to deviate from that decision.

What would be the best way to indicate the context in which these fields are required? What should I add to the label? Is there a better way to handle this kind of situation?



Answers 1


If it is hard to change and you can provide some form(s) of side-band training for the users, giving extra time to those who aren't familiar with software in general, stick with what you have as you admit it may be the only option. Not really pushing the UX envelope there though!

To indicate the fields are required for finalization but not required for saving, a straightforward approach: add complementary information to the label such as "only required for finalization" and have it displayed always within the form. An alternative approach, really the standard approach, is to flip your question and add to the labels of all fields that are not required for finalization to indicate they are "optional". Your developers seem to be doing it wrong.

You could go further to add a helpful hint, perhaps a balloon that provides a little more information to make it clear that users can indeed save without having to provide a value. That hint mechanism will probably be useful for other aspects of this form and other forma in the system.

Disable fields that the user cannot edit. Group them with a note indicating the staff member they need to contact, even provide a button to automatically send that email to help the user.

straya
straya
January 31, 2020 13:32 PM

Related Questions


Accessibility and required form fields

Updated January 26, 2017 14:06 PM

Using asterisk (*) vs required

Updated February 25, 2016 01:07 AM