Hi Anna
From Open API perspective, we try to enable business, not restrict it. So at the level of user guide the APIs don't in general proscribe operations such as DELETE. It would be up to a specific implementation of an API to give conditions as to when e.g. a Party Role can be deleted.
Regarding the related entities pointing to a potentially deleted entity, let's consider Product Order as a more plausible use case. We have Product (inventory) that has a reference to Product Order (e.g. the order that created the product, or perhaps a pending order on the product). Orders might be archived and deleted after a certain time interval, to optimize storage space. So if a product is retrieved it might have orphan references. This can be dealt with in a number of ways:
- As part of deleting an entity you scan all the entities that refer to it; this could be quite expensive and you may not even have control of all the places that the entity reference has reached
- As a consumer, be resilient if entity refs point to entities that cannot be retrieved.
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: Jan 18, 2022 04:35
From: Anna Kozłowska-Jarosz
Subject: TMF 669 Party Role Management
Hi All,
I have a question related to DELETE operation in Party Role Management API, if this action should be available only for some statuses like e.g. "draft" of party role or it is available always.
If always what exactly does it mean for related entities for this party role?
------------------------------
Anna Kozłowska-Jarosz
Comarch S.A.
------------------------------