Dear Community Members,
I am dealing with a use-case where I need to create a service order entity using "POST /serviceOrder". Here, to store the party details, I should ideally use the TMF632 entity by reference in "relatedParty" attribute.
However, since the TMF632 API is a strategic solution which might be implemented in future for my project, I am wondering if I may use the "relatedParty" attribute to get the party details by value. I need a very limited party-detail for now in my TMF641 entity. Also, there is a very limited set of party present to deal with - at present.
I have provided an example here (a snippet of TMF641 entity). Your views are welcome. Many thanks!
{
"correlation-id": "123e4567-e89b-12d3-a456-426655440000",
"data": {
"relatedParty": [
{
"id": "1",
"name": "Agent1",
"role": "RequestingAgent",
"@referredType": "Individual"
},
{
"id": "1",
"name": "NameExample",
"role": "contactName",
"@referredType": "Individual"
},
{
"id": "1",
"name": "EmailExample",
"role": "contactEmail",
"@referredType": "Individual"
},
{
"id": "1",
"name": "TelephoneExample",
"role": "contactTelephone",
"@referredType": "Individual"
}
],
------------------------------
Gaurav Sinha
Infosys
------------------------------