Feedback: New Field Restyling - Optional Fields

Alex Gregorio 7 months ago in Productivity Management updated 1 day ago 6

With the switch to no longer labeling required fields with an asterisk and instead labeling non-required fields with "...-optional" is creating some confusion for users. Some of these fields are read-only fields -- this is a change that we are not looking to reconfigure and would prefer some flexibility around the labeling or required vs. non required rather than simply switching the configuration. 


Aprimo has received feedback from many customers regarding this particular topic.  I know of many more customers who would vote on this Idea if they new it was here.  Based on this we have been evaluating alternative options for handling the "Required" field designation and have a new design we plan to implement.

We will be placing a "Required" indicator tab next to each required field on the page when it is initially loaded and does not have a value.  As shown in the screenshot below.  This will make seeing what fields are required very obvious and easy for the users to notice.  

However, we know if showed this all the time it would also make the page very busy.  Therefore, once a user selects a value for a required field the "Required" indicator will be hidden on the page.  This way as the user completes the page they will be able to visual see which fields are still missing that require an entry.  As shown on the Lifestyle Segment field.  In the top screen shot it has the "Required" indicator when <not selected>.  In the below screen shot, a value of Youth has been picked so the "Required" indicator has been hidden.

This work is assigned to a team.  Development should begin later this quarter with a goal to release in March or April.  We want this change in place well before the New Field Restyling feature become activated for all customers in June to give customer time to train their users on how the pages will look once that is activated.

Eric, this is great news. Can we expect to see non-required fields to be "blank" or will they still be labeled as optional?

Hi Eric, 

Following up on the above question. If I remember correctly, you mentioned that required fields will be labeled as required and non-required fields are going to be labeled as optional. How will read-only fields be treated? Today we are seeing them being labeled as optional however, we'd like to ensure we're not labeling those fields since there is no action needed from the user.

While I absolutely love the new, clean look of styling for the campaign fields and just overall look of the page, I think the page has gotten a little too clean.  I have to agree with both Alex and Christine that there is no longer a distinct difference between required and non-required fields and this has a huge potential for creating user confusion.

We have been testing it also and run into the same issues.

Users are also confused because required EA’s look the same as read only EA’s.

I agree with Alex's comments.  As I have been testing out the New Field Restyling in our Sandbox, I am noticing there is no real standout as to what the required fields are.  Our users look for the recd asterisk.  This will for sure cause confusion to our users.