Prevent Broken States by Deletion / Editing

[richardtreier]

Feature Request

Description

The Core EDC has loose coupling of entities. One can delete an asset for a live contract agreement and have future transfer processes fail.

We could either design our own foreign key constraints (problematic due to existing loose data) or especially enforce relations in our API Wrapper endpoints.

This would allow us to prevent not well defined broken states such as #228

depends on #364

this is an alternative solution to #387

Check:

• Assets can be deleted while referenced by a contract definition, and can later be re-created..
• Assets can be deleted while referenced by a contract agreement (!), and can later be re-created.
• Contract Definitions can be created with Policy Definitions that don't exist.

Tasks

Beta Give feedback

1. Prevent Asset Deletion and Asset Editing for data offers with existing negotiations IN_PROGRESS or SUCCESSFUL.
2. Prevent Policy Definition Deletion and Policy Definition Editing for data offers with existing negotiations IN_PROGRESS or SUCCESSFUL.
3. Deleting Contract Definitions has no impact on existing Contract Agreements. Do we have any interactions that we need to be aware of?
4. Add "boolean canDelete; String cannotDeleteReason;" to the API Wrapper Dtos in question.
5. Implement in UI