>global Globals are not a type unto themselves, but a scope for the other types. This seems most useful for tickets where you want a CF to be available for most if not all of your queues (and if not all, it's presence is not a problem in the others) e.g; a Tags field.
The ticket and transaction CFs can be queue-specific or global. >queues No idea. >ticket Non-transaction information e.g; custom status, reference ID for an external system (Nagios, purchase order) >transactions Track your staff's stress on a per interaction basis, or stash some value for a scrip to operate on, etc. >users Say you want to store a fax number as well as the already supported pager number, or the person's birthday, SSN (shame on you), etc. _______________________________________________ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [email protected] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
