[Concept] Enhancing Transparency and Management of EDC Contract Agreements and Policies

[ds-mwesener]

As a system administrator, I want a mechanism to log all contract agreement IDs associated with EDC assets and policies, so that there is clear transparency and historical tracking of changes and updates.

Blocks: https://github.com/eclipse-tractusx/traceability-foss/issues/1064

Hints / Details

• The history should reflect a list of contract agreement IDs with dates to keep the history of old contracts transparent.
• There should be a clear delineation of assets and policies that require updates and those that do not.

Process

1. Call the registry API including a filter to get the relevant asset by globalAssetId. (Ask Jaro for specific details.) 1a. Ensure access to the registry element ID is maintained as it will be needed along with the globalAssetId.
2. Extract the EDC asset ID from the subprotocol body. 2a. Ensure access to this information is maintained along with registryId and globalAssetId for future updates.
3. Filter and retrieve contract definitions using the EDC asset ID to check if the current policy matches the existing one. If the policy remains the same, no new contract is required. If not, proceed to create new EDC asset, EDC policy, and EDC contract definition as needed.
4. Create new EDC contract definitions as described in step 3 if necessary.
5. Utilize the registryId associated with the globalAssetId for updates.
6. Update the registry subprotocol body with the new EDC asset ID to reflect changes.

Acceptance Criteria

• Create a concept which defines the flow including request examples.
• The system logs every contract agreement ID whenever there is an update to the associated EDC assets and policies.
• The system provides a history view where each entry includes the date of the contract and its associated ID.
• The system ensures that EDC assets that do not need updates are not updated.
• The system updates the EDC policies and contract definitions only if there are changes in the policies.
• For notifications we need to define which policy should be used for contractNegotiation, this could be a button in the policy management table which sets a policy as active (just example)
• Mock has been created how a policy will be set to active for notifications.
• Datamodel of assets updated for reflecting a contractAgreementId history

Out of Scope

• Managing or updating registry APIs or other systems not directly handling EDC assets and policies.
• Detailed mechanisms of how external systems interact with this update mechanism.