-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Norbert,
> How we should run export to a specific ranges - CI - if a specific > changes happened ? (API, or triggering a function, etc...) for this requirement you could use CI-events, which will probably be available in the next ITSM-release, or respectively are already available in OTRS::CiCS::ITSM. The post-event-handler should check after a successful versionadd if one of the attributes of interest has been changed and if so runs your export action. regards, Torsten - -- Torsten Thau, Dipl. Inform. c.a.p.e. IT GmbH - Annaberger Str. 240 - D-09125 Chemnitz phone: +49 371 5347 623 cell: +49 176 66 680 680 personal pgp-key: 0x93E0A174 company pgp-key: 0x292F987D fax: +49 371 5347 625 http://www.cape-it.de AG Chemnitz - HRB 23192 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkuptnYACgkQvXo8m5PgoXTjvQCfUf3cCB73C9nv0STK5Hpoo/m3 8DkAn2B/rMtAB1mqfizBDs/DLCXx1TAK =cqgm -----END PGP SIGNATURE----- --------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW! http://www.otrs.com/en/support/enterprise-subscription/
