Expand my Community achievements bar.

SOLVED

Required Fields outline

Avatar

Level 2

Good Morning Everyone,

Got a quick question. I'm sure this one an be done somehow. I created a form and the required filds that are not entered get surround in a big RED box.. Can I change that color??? It's really bright.

Thanks ahead of time.

Lucy

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

That is an Acrobat/Reader setting. On the Edit /Preferences menu, choose Forms and you can adjust the "Required Fields Highlight Color" in the HighLight Color  Section.

Paul

View solution in original post

7 Replies

Avatar

Correct answer by
Former Community Member

That is an Acrobat/Reader setting. On the Edit /Preferences menu, choose Forms and you can adjust the "Required Fields Highlight Color" in the HighLight Color  Section.

Paul

Avatar

Level 2

Thanks a whole bunch! This did work for me but on my machine only. Is this one of those things that everyone that opens the form with have to change the highlighted color if they don't like the red? Is there a way to make it automatically pick up a different color?

Thanks Lucy

Avatar

Former Community Member

no. the only you can either "highlight" fields or not. thats the only two options.

Avatar

Level 2

I didn’t' think so. Still had to make sure. Thanks a bunch for your help.

Avatar

Former Community Member

I have a question,  I am using liveCycle designer/javascript and what I am trying to accomplish is when the PDF open can only the required fields background be colored and the optional fields not?  

Avatar

Level 10

Hi,

First you would need to add JavaScript to the docReady event of the root node (normally "form1").

app.runtimeHighlight = false;

This will turn off the standard highlighting.

Then the simplest way would be to set the background of the mandatory fields manually in LC Designer.

Hope that helps,

Niall

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----