Thanks Adinan
This is a known defect in the CTK, since
engagedParty is indeed a mandatory attribute of PartyRole (it's the party who's playing the role, you cannot have a party role without a party) - and since Customer is a specialization of PartyRole also Customer should have mandatory
engagedParty.
At some point the CTK will be fixed, not quite sure how and when, since this does impact API implementers who have already achieved formal conformance for TMF629.
------------------------------
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: Nov 18, 2020 13:40
From: Adinan Sousa
Subject: TMF 629/632
Hi Heinz,
Just be aware that the current CTK available for TMF629 via Open API table is not according to TMF specification document, since that on the specification the mandatory attributes are name and engagedParty, but on the CTK only name is required as mandatory.
------------------------------
Adinan Sousa
Ericsson Inc.
Original Message:
Sent: Nov 17, 2020 09:06
From: Jonathan Goldberg
Subject: TMF 629/632
Hi Heinz
Published assets, including CTKs, are available via the Open API table here. You will see that both APIs have CTKs available.
In case you are looking for other APIs that are still in progress, you can look at the early access table here.
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: Nov 17, 2020 06:30
From: Heinz Sandermann
Subject: TMF 629/632
Dear Community,
Is there any CTK package available to check TMF conformity of TMF 629 and 632 API implementations (Release 19.0.1) ?
Regards
Heinz
------------------------------
Heinz Sandermann
Deutsche Telekom AG
------------------------------