Service Desk Practitioners Forum
cancel
Showing results for 
Search instead for 
Did you mean: 

New boolean fields are tri-state - HPOV SD 4.5 SP27

SOLVED
Go to solution
Highlighted

New boolean fields are tri-state - HPOV SD 4.5 SP27

Hi all.

I have added some new boolean fields (check-boxes) in Service call forms. When these boxes are checked, they have three states, checked, unchecked, and greyed. How do I remove the greyed state? It baffles users.

The "original" out-of-the-box boolean fields do not have this third (greyed) state, only new ones that I have added in "Custom fields".

I have tried to set the fields as "mandatory", and also set default state to "No" in the corresponding templates, without help.

We use Client 2008.

Any help will be greatly rewarded with points :-).

Michael
5 REPLIES
The Pike
Honored Contributor

Re: New boolean fields are tri-state - HPOV SD 4.5 SP27

Michael,
Check this out:

http://support.openview.hp.com/selfsolve/document/KM770904

Three workaround options are offered in that document.

Points are welcome.

The Pike

Re: New boolean fields are tri-state - HPOV SD 4.5 SP27

Thanks for the link! I didn't know about this document.

However it did not solve my problem :-(. I have set the fields mandatory but this didn't make any difference, neither did setting the fields to No in the templates. Changing the checkbox to Yes/No is no option I'm afraid.

Michael
The Pike
Honored Contributor

Re: New boolean fields are tri-state - HPOV SD 4.5 SP27

Did you restart the appserver(s) after creating the custom field and setting it as mandatory?

Points are welcome.

The Pike

Re: New boolean fields are tri-state - HPOV SD 4.5 SP27

Hi again!

No, haven't restarted the appserver. Will try at next possible opportunity.

Thanks!
Michael
The Pike
Honored Contributor
Solution

Re: New boolean fields are tri-state - HPOV SD 4.5 SP27

Yup, I just created a boolean custom field in my sandbox server and it went from the three states to only two after setting it as mandatory and restarting the appserver.

So the workaround is effective.

Points are welcome.

The Pike
//Add this to "OnDomLoad" event