Znuny Open Source Ticketsystem

Giulio , thanks for helping! Generic Interface is available since the 3.2.x versions as a core part of OTRS, no add-on required... as jojo suggested you should be able to configure OTRS as invoker and trigger the communication on specific ticket events To configure OTRS as invoker, there have to be...

Thank you very much, jojo!
I'll try it.

It seems like OTRS Ticket Connector doesn't have any WSDL, so I can't easily consume its methods, for instance, in a .NET app.

Does anybody know where I can get WSDL for Ticket Connector? Or maybe there is .NET client class for it?

Why are you not using webservices and trigger communication by events? This is obviously my second option. But AFAIK I need to implement custom invoker to use this aproach since there is no one out-of-the-box. And, in addition, I have to implement a SOAP service that this invoker would send message...

What can I say in my turn? Your point of view can take place for sure. But from the other side, why intentionally restrict use cases of a system when there is no any visible special need? For me as a customer of OTRS and a developer, it is a little bit strange why I can send, for instance, a ticket ...

This is not about agents, but the part of integration. Emails is supposed to be used in another system and have to: 1. indicate the fact that something is changed in a ticket 2. contain comprehensive set of fields used by another system including all the articles and all the attachments of the chang...

I need to include all the articles and all the attachnents of a ticket to the email notification when ticket is created or changed (added article or attachment). I tried to setup the Notification (Event) and use <OTRS_CUSTOMER_*>-like fields but it seems like there is no suitable fields for my situa...