Thanks a lot for your reply.
I think we have 3 different scenarios or solutions:
-Change the API specifications and not create a related party.
-The party is not created previously. In this case you can create an associated party, but an additional attribute is needed, the party type, as an Individual or Organization. Both have common attributes and relationships, but also specific items and class relationships.
-The party has been created previously, in this case the additional parameter could be the party. id (Indivdual. id or Organization. id) indistinctly.
But I think the API needs the additional parameter, or do not create the party.
Regards.
------------------------------
Antonio Revuelta
Beesion Technologies
------------------------------
Original Message:
Sent: Sep 12, 2018 04:42
From: Hongxia Hao
Subject: TMF629 Customer Management API. POST Operation and Party.
Hi,
As you said , the name is the mandatory attribute. I think you can add other operational attributes not only name . or do you think which attribute should also be set to be mandatory ?
Regards,
Helen
------------------------------
Hongxia Hao
Huawei Technologies Co. Ltd
Original Message:
Sent: Sep 06, 2018 03:35
From: Antonio Revuelta
Subject: TMF629 Customer Management API. POST Operation and Party.
Hi,
Reviewing the API specification I realized that in POST operation, creating a Customer, the only mandatory attribute is name. With this name the customer and the party are created. I agree with that (to create the customer and the party at the same time). But it's impossible to deduce only with name if you have to create an extended party type Organization or Individual. So we need another attribute or create the party previously using the party API and create the customer using the party id (as well as attribute).
Thanks a lot for your help or ideas.
Regards.
------------------------------
Antonio Revuelta
Beesion Technologies
------------------------------