The API supports two modes:
- prepare and later mark for sending (in two operations)
- submit and mark for sending in a single operation
This reflects the business requirements that have been a basis for the work.
The use of sendTime is to my understanding independent of the above.
For information, in the ongoing work on 19.5 it is considered to consolidate in one operation and to include a new boolean property "readyToSend" (or similar). Again, the use of sendTime is independent of this.
------------------------------
Knut Johannessen
Telenor ASA
------------------------------
Original Message:
Sent: Sep 04, 2019 04:24
From: Ludovic Robert
Subject: TMF 681 Communication API - CREATE Notification & SEND two operations
Hello,
+ @Knut Johannessen who took the lead on this API.
Best regards
Ludovic
------------------------------
Ludovic Robert
Orange
Original Message:
Sent: Sep 03, 2019 09:32
From: Rabinder Devnani
Subject: TMF 681 Communication API - CREATE Notification & SEND two operations
Hi,
Was going through "TMF681_Communication_API_REST_Specification_R18.0.1" and found that there are 2 API operations for Communications API i.e.
"POST /communicationMessage" & "POST /communicationMessage/send". I want to understand requirement of creating 2 separate operations and not using only "send" operation to save the message and send to the receiver Related Party in a single operation?
I am assuming that operations "POST /communicationMessage" & "POST /communicationMessage/{ID}/send" are used in conjunction first to create CommunicationMessage and then to send the created one.
Does it related to scheduled notifications with "SendTime" in future?
@Ludovic Robert & @Jonathan Goldberg your thoughts?
------------------------------
Rabinder Devnani
Sterlite Technologies Limited
------------------------------