On Fri, 18 Mar 2005, Martin Edenhofer wrote: > Steve Churchill wrote: > > I'm looking at using the FreeTextFields here, but these seem to only be > > available as associative hash arrays. While I find this useful, and > > like the combo box functionality, I'd still just like some extra "free > > text" fields associated with each ticket. Each of these will need to be > > new fields in the ticket table of course. I'll try and develop this so > > adding more fields is a matter of changing your for loop count.
If I can interject, changing the free-text field count is entirely the wrong way of handling this. It results in the same problem as hard-coded attachment counts, etc. There should really be a new table for "free_text_types" that allow admins/agents to create new field definitions. Each row in the table would define a type that would be referenced in another table, "free_text(s)". Each row in this table would be a unique free_text that would refer back to the ticket_id for the ticket it's associated with, and have a foreign key back to the free_text_types table. Not only does this scale by just looping through the array of $sth->fetchrow_hashref(s), but new free_text entries can based on existing "types" by referencing back to the free_text_types table and forming the basis for a drop-down. Does my rambling make any sense? :) -- Jason Dixon 301.286.8635 voice NASA / Goddard Space Flight Center [EMAIL PROTECTED] AMTI, Inc. Building 28, Room S212 Code 931 _______________________________________________ OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
