Hi Martin, Am 20.08.2010 09:46, schrieb Martin Edenhofer:
Hi Thomas,
On 19.08.2010, at 12:58, Thomas Kaltenbrunner wrote:
The major change is the completely new interface (moved from html with table layout to clean markup and css).
Regarding Perl-API, some small changes, but almost compatible to OTRS 2.x
PS: Can you point me out what you want to create/change? So I can write you what steps you need to go.
I want implement a function to send a summary of the ticket to an email receiver. At the moment I am in a very early stage and try to get into the architecture of the system and find a starting point. I think I will first have a deeper look into the docs and then start with the package example.
One more question. Who should trigger the sending of this ticket summary? An agent via the web interface or because a ticket is escalated?
First use is sending via the web interface by an agent. May be this function is not needed often, when OTRS is better integrated in the organisation and the daily work. Another point is, that I am not satisfied with the given possibilities of displaying or printing a summary of the ticket. It contains to much details and the progress of the work is not clearly outlined. It is nice to have boxes in the GUI for every step or action of a ticket, but scrolling down one text box with several sections I would like more, since I could see more text in one sight without clicking or further scrolling Thomas
Thomas
-Martin
This should definitely be implemented as a package, without changing any of the core OTRS files.
OK.
Thanks
Gruß Thomas
Blog: http://edenhofer.de/
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
-- OPC® cardsystems GmbH Mobil: +49 151 52628082 Skype: tj-opc Zentrale: +49 651 8408 0 Geschäftsführer: Torsten Hülsmann, Dipl.-Ing. (FH) Klaus Dieter Schömer Registergericht: Amtsgericht Wittlich HRB-Nr.: 3903