Hi Konstantin
I think I may have answered too hastily, apologies for the confusion - I have now looked in more detail and it seems that AgreementItem is a sub-entity of Agreement, and not an independently managed entity at all (and so AgreementItem has no ID or href). So in order to be addressable (it is used in Product) the AgreementItemRef should actually point to the Agreement (i.e. the id, href are of the Agreement) and then the agreementItemID in the Ref is an internal index of the item in the agreement.
BUT - AgreementItem does not have this index :(
So we will need to fix this - I will update the JIRA accordingly, but I cannot commit to when the fix to the API will be made, since I am not the subject matter expert for this API.
Again apologies for the confusion and I hope it is now understandable.
------------------------------
Jonathan Goldberg
Amdocs Management Limited
------------------------------
Original Message:
Sent: Oct 02, 2019 09:53
From: Konstantin Tarasov
Subject: TMF 648 19.0.0 AgreementRef and AgreementItemRef
Hi Jonathan,
Thanks for your answer.
Have you considered keeping agreementId in AgreementItemRef?
An Agreement Item always has a context of the Agreement to which it belongs and it would be helpful to have agreementId in AgreementItemRef.
------------------------------
Konstantin Tarasov
Netcracker Technology
Original Message:
Sent: Oct 02, 2019 09:26
From: Jonathan Goldberg
Subject: TMF 648 19.0.0 AgreementRef and AgreementItemRef
Hi Konstantin
We discussed this just now in our API team meeting - there has been an error in our schemas that caused the duplicate attributes (name + name, and id + agreementItemID). We have an open JIRA issue for this so hopefully it will be corrected, meaning that agreementItemID will be removed and the double name will be removed.
Generally, Ref entities are pointers to full entities, and will have id, href, and name - specific ref entities may have a small number of additional attributes as determined by design needs.
So AgreementItemRef.id should contain the id (primary key) of the agreement item (and agreementItemID will hopefully be removed).
Hope it helps
------------------------------
Jonathan Goldberg
Amdocs Management Limited
Original Message:
Sent: Sep 24, 2019 13:57
From: Konstantin Tarasov
Subject: TMF 648 19.0.0 AgreementRef and AgreementItemRef
Hi team,
In 19th version of Quote TMF API a new class AgreementItemRef has been introduced.
The description is a bit confusing:
------------------------------
Konstantin Tarasov
Netcracker Technology
------------------------------