On 07/24/2010 11:07 PM, paul gore wrote:
Yes, I meant notifications section. My problem is I do not see any customer related notifications available there, only agents. I have seen similar problem reported here with no reply. So is it a bug? Can it be fixed?
Its not a bug of which I am aware. The notifications are store in your database backend under the table "notifications". If you specified an OTRS specific table name prefix, it will be "${prefix}notifications". For example: If you made "otrs_" your prefix, the notifications table will be called "otrs_notifications". Make an SQL query to ensure the notifications are in that table. The field "notification_type" will show you the name of each notification. For example: The record with notification_type "Agent::NewTicket" will contain all the data for notifying Agents about new tickets. When you first installed OTRS, if you used the web installer, it will have run several sql statements stored as files to set up the database. If you installed manually, you would have run the sql statements yourself. The statement files should be in your otrs directory in scripts/database. The statement file that inserts the notifications data (and possibly lots of other stuff, too) should be called otrs_initial-insert.sql. Don't just blindly re-insert all that data, either. Don't assume I know what I'm talking about. Have a good look into the contents of the file. You may only need to pick out a couple sql inserts to put back the default notification in the language(s) you want. Good luck! (-: