[SOLVED] TicketFreeText::DefaultSelection to Null or Blank

Moderator: crythias

Locked
ptay
Znuny newbie
Posts: 85
Joined: 13 Jul 2010, 18:55
Znuny Version: 5.0.10

[SOLVED] TicketFreeText::DefaultSelection to Null or Blank

Post by ptay »

Thanks jojo, putting a blank in KEY field and "-" in CONTENT field defaulted to "-" in drop down and required one of the other valid entries since I set bit to required. This is exactly what I wanted, thank you much!

Anyone know if I can use a null/blank value for TicketFreeText::DefaultSelection in TicketFreeText?

The field is mandatory but I'd like to default the value to null/blank so users must select one of the valid choices (null/blank not being valid).
Last edited by ptay on 19 Jan 2011, 01:02, edited 2 times in total.
Test:: OTRS 5.0.10 w/MariaDB 5.5.47 backend on RHEL7
Prod:: OTRS 5.0.10 w/MariaDB 5.5.47 backend on RHEL7
jojo
Znuny guru
Posts: 15020
Joined: 26 Jan 2007, 14:50
Znuny Version: Git Master
Contact:

Re: Set TicketFreeText::DefaultSelection to Null or Blank

Post by jojo »

just set a value pair emtpy and a dsh (-) in the list. this will be the first in Order and will work. No need to use TicketFreeText::DefaultSelection
"Production": OTRS™ 8, OTRS™ 7, STORM powered by OTRS
"Testing": ((OTRS Community Edition)) and git Master

Never change Defaults.pm! :: Blog
Professional Services:: http://www.otrs.com :: enjoy@otrs.com
Locked