
Hi, How is the "Required" enforced in FreeText fields? For example, in Ticket::Frontend::AgentTicketFreeText###TicketFreeTime, we can use 0, 1 or 2 for content of a key. If we choose 2 there for content of a key, what will force this field to be populated? Thanks, Ugo

Hi Ugo, I believe there is actually a bug in OTRS in the way it is treating obligatory free text fields. I demonstrated a system the other day where I set a new text field on EmailNew and made it a category 2. When I enter the new ticket the free text field is there, but it allows me to leave the text field empty. I need to verify on another system, but this may also be what you are seeing. Arnold. Op 10-08-11 20:47, Ugo Bellavance wrote:
Hi,
How is the "Required" enforced in FreeText fields?
For example, in Ticket::Frontend::AgentTicketFreeText###TicketFreeTime, we can use 0, 1 or 2 for content of a key. If we choose 2 there for content of a key, what will force this field to be populated?
Thanks,
Ugo
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs

Le 2011-08-10 14:50, Arnold Ligtvoet a écrit :
Hi Ugo,
I believe there is actually a bug in OTRS in the way it is treating obligatory free text fields. I demonstrated a system the other day where I set a new text field on EmailNew and made it a category 2.
From what I've seen, here is what I think: - Mandatory field is automatically created and active on a ticket. When using the client interface, if you show this field, you'll see an asterisk besides it. - Optionnal field is shown with a checkbox to enable it in the client interface.
participants (2)
-
Arnold Ligtvoet
-
Ugo Bellavance