On Fri, May 27, 2005 at 11:36:20AM +0200, Victor Rodriguez Cortes wrote:
With OTRS you don't need to access the database directly, except in very rare occasions (disaster recovery, corrupted tables, etc).
I beg to differ. Having relational integrity constraints is an important part of having and maintaining a consistent database.
To disable the default queues you have 2 options:
- Rename them to something usefull for you. - Disable them, so they won't be shown (mark as invalid in admin interface).
Anyway, they can be used for things not related directly to your clients, as 'Junk' to store spam (and delete it automatically with the generic agent) or "Postmaster" to store system or administrative messages. Also, it's usefull to have some test queues, to test all kind of things without disturbing your clients queues. I've renamed 'Raw' and 'Misc' as 'TestQ1' and TestQ2' ;-)
OK so is there a way to let the queues exist and be seen by agents, while hiding them from customers ? bye Jerome Alet