Let me brief about my requirement.
Here we are going for TMF compliance conversation of existing solution. We need to prepare one TMF comply API layer that will communicate southbound APIGateway/Middleware layer and further it will call existing legacy billing/charging/CRM system.
So my TMF API layer will trigger single API of APIGateway/Middleware layer while it will be distributed in multiple API call behind the middleware.
Here middleware layer is asking to pass all the parameters in single API call and they have below structure for contactList & addressList details.
Please suggest what would be better for my need. Even If you can share just your to be schema object instead of full swagger where I can incorporate these changes then also its fine for me, I will take just reference from your sample.
What will be your view to extend Customer API with below place object extension extending additional inputs for my address/[List Object]?
Original Message:
Sent: Jun 21, 2023 02:26
From: Jonathan Goldberg
Subject: Address details of Customer: TMF629_CustomerManagement
I cannot share the v5 assets yet, they are still in internal review. I hope that some time in the next few weeks they will get published as beta, but I cannot promise.
Please note also that this v5 change is a breaking change, so we would not be able to "downport" it to the v4 APIs.
Not sure I understand your question "should I use same for address".
------------------------------
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: Jun 20, 2023 11:26
From: Chetan Patel
Subject: Address details of Customer: TMF629_CustomerManagement
Hi Jonthan,
In v5, ContactMedium extension with items is really good for my requirements.
Here we have additional challenges that we need to fulfil ContactMedium & Address as a separate list object and both have additional attributes/Geographical attributes. for example,
ContactMedium have boolean attribute like isactive, hasExtension, Date attributes like createDate, updateDate, key-value pair future use attributes
Address have landmark, region, regionid, building name, building number, , key-value pair future use attributes.
As I understood from your response, item sub-class under ContactMedium base-class may be cover only ContactMedium additional line items.
Can you please guide, should I use same for address?
If you have v5 spec/swagger, then can you please share with me?
------------------------------
Chetan Patel
Tech Mahindra Limited
Original Message:
Sent: Jun 20, 2023 10:28
From: Jonathan Goldberg
Subject: Address details of Customer: TMF629_CustomerManagement
Hi Chetan
Assuming that you are referring to published v4 APIs, Customer (and other entities) have an array of ContactMedium, where each ContactMedium has a set of MediumCharacteristics. So you already have the capability for multiple addresses.
"contactMedium": {
"type": "array",
"items": {
"$ref": "../Common/ContactMedium.schema.json#ContactMedium"
}
},
In v5, we are refactoring ContactMedium to be a base class and specific subclasses, so you'll have a specific Address Contact Medium, that includes the address properties and (importantly for your use case) a link to an underlying GeographicAddress.
------------------------------
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: Jun 19, 2023 07:19
From: Chetan Patel
Subject: Address details of Customer: TMF629_CustomerManagement
Hi @Koen Peeters
We are looking for the same information. Here we may need to manage multiple addresses of customer as well as each address have additional address attributes that's not available in TMF629, how can we handle it?
Additional attributes like landmark, region, regionid, building name, building number, demographics, so do we have any schema object that fulfil all these information or should we extend MediumCharacteristic with additional attributes?
Can we convert MediumCharacteristic as a List in TMF629 implementation?
------------------------------
Chetan Patel
Tech Mahindra Limited
Original Message:
Sent: Oct 01, 2019 14:12
From: Koen Peeters
Subject: Address details of Customer: TMF629_CustomerManagement
Hi,
Address details can be provided as MediumCharacteristic.
Regards
------------------------------
Koen Peeters
Ciminko Luxembourg
Original Message:
Sent: Sep 27, 2019 09:40
From: Sheeja Soby
Subject: Address details of Customer: TMF629_CustomerManagement
Hi ,
We are using TMF629_CustomerManagement and we could not find the address details of a Customer captured in any of the entities within Customer Management. Can you please guide as to where is this information captured ?
Regards,
Sheeja
------------------------------
Sheeja Soby
Infosys
------------------------------