Hi Kalpana
I'm not an expert in the area of Change Management.
But it seems to me that the Change Management API is responsible for managing the whole process of a change, including approvals, mods, rejections, etc.
The actual communication of such to the end customer would seem to need to go through Communication API, since this abstracts the way we communicate with a customer (preferred means of communication, times of day and days of week for communication, etc.)
So I think I agree with you that you should use the Communication API.
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.
------------------------------
Original Message:
Sent: Jul 21, 2020 07:43
From: Kalpana HV
Subject: TMF681 Communication API Usecase
Hi,
We have below requirement from our client
- To receive a notification for a planned change (Client need to receive notification from us(service provider))
- To receive a notification for a rescheduled change
- To receive a notification for a completed change
- The notifications shall contain:
- The start date/time of the change
- The end date/time of the change OR the duration of the change
- The impacted Colt circuit ID
- Details of the change
Note: Notification will be in the form of emails
I believe Communication API to be used for this purpose with below options.
POST /communicationMessage and POST /communicationMessage/{id}/send
or
POST /communicationMessage/send
Please let me know whether this is correct or Change Management API to be used?
Best Regards,
Kalpana
------------------------------
Kalpana HV
Colt Technology Services
------------------------------