Is there an agreed pattern to support changes to a related party in a TMF API.
For e.g. if the Org or Individual associated with a Product or Service changes, how do we request the change in the TMF APIs.
Is it a Product Order or Service Order of type modify or is there any other pattern.
If it is an order then how do we indicate that the related party has changed?
I'm not quite sure what you are referring to. It could be:
For the second situation, presumably you would PATCH (json-patch or merge-patch) the relevant reference to the related party in the containing entity
The first situation is more tricky, since it could be that the data change has side effects (e.g. in my example on tax calculation). I don't think this is a pure API concern, it's more of a system design consideration. For example, you could have some listener that consumes events on Party, and which would take appropriate action in the case of a significant change.
Hope it helps
Thanks Jonathan. I was more thinking of the 2nd scenario where the contact has changed.
We could patch the Product or the Service object with the new party as you suggest.
However should we use the Inventory API i.e 637 or 638?
If there are no side-effects due to the substitution of a different related party, then yes you would use PATCH in 637 or 638. But it is possible, especially for Product, that the substitution of a related party could itself trigger re-evaluation of qualification, meaning you would be in an ordering situation.