Open APIs

My source system currently  cannot send multiple attachments when syncing tickets data to Target system via the TMF API. So as a workaround we are simply include pointers for those attachments with the ticket, then expecting  target system to re-query  Source system on another GetAttachment API ( this would be different REST API)  to get the attachments.

Just checking if this would be TMF compliant or not or any other way to handle this ?

------------------------------
Prashant Kumar
TO BE VERIFIED
------------------------------

Hi Prashant

TMF655 is the Change Management API, there is no mention of Ticket in this API. Perhaps there is some confusion with the Trouble Ticket API TMF621?

At any rate, there is currently no concept in TMF Open API of Attachment as a managed resource, so there is no GET Attachment end-point. We know that this is a gap, but unfortunately it is not going to be addressed in the near future.

However, if the contents of the attachment are stored in (say) a content management system (as opposed to being embedded within the Attachment resource, you have a reasonable workaround. The URL attribute of Attachment can be set to point to the actual attachment contents in that system, and then your target system can retrieve the contents directly using the API. A URL might look something like this:
https://CMS.mycompany.com/docloader.aspx?action=view&docnum=66333555
Hope it helps

------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
------------------------------