Provide EDC Contract API for FE

[ds-jleyh]

As an API Requester of Trace-X
I want to provide data of contracts
so that users can see contracts to their assets

Hints / Details

• The concept including a sequence flow is documented here: Contract management concept & design
• https://github.com/catenax-ng/tx-item-relationship-service/blob/main/docs/concept/%23322-Provisioning-of-contractAgreementId-for-assets/%23322-Provisioning-of-contractAgreementId-for-assets.md

Clarification

Currently there is a technical question which needs to be answered before we can estimate this story:

Initial we thought we can retrieve the contractAgreementId based on the globalAssetId. Therefore we need a relation or some kind of a mapping between those variables. Plan is to have a small technical discussion with two developers. Lucas Capellino / Maximilian Wesener / Janice Leyh to clarify how to address this question. Should be ready for estimation for next refinement session on 9th January.

Acceptance Criteria

• the attributes contract ID, Counter party address, creation date, state and policy are provided
• the processed data of the management API can be accessed through a new API: GET/contracts/{assetID}
• the new API is documented
• the new API makes 2 Requests to get attributes: POST/management/v2/contractagreements/request & GET /management/v2/contractagreements/{ContractAgreementId}/negotiation
• payload of the requests is mapped into a domain model

Out of Scope

• Attribute EndDate: At the moment, the end date can't be taken from the edc, because the edc doesn't manage usage policies.

[ds-jleyh]

couldn't assign @ds-lcapellino

[jzbmw]

I also could not do that

[jzbmw]

eclipse-tractusx/item-relationship-service#370

[ds-lcapellino]

Concept:
https://github.com/catenax-ng/tx-traceability-foss/blob/main/docs/concept/%23638-contractagreement-admin-view/%23638-contractagreement-admin-view.md

[ds-lcapellino]

Open questions:

1. mix as-planned and as-built assets in contract view?
2. Default view in contracts on first click on page?

[ds-lcapellino]

Updated acceptance criteria

• the attributes contract ID, Counter party address, creation date and state are provided
• the processed data of the management API can be accessed through a new API: POST/contracts with a pageable and filterable Object
• the new API is documented
• the new API makes 2 Requests to get attributes: POST/management/v2/contractagreements/request & GET /management/v2/contractagreements/{ContractAgreementId}/negotiation
• payload of the requests is mapped into a domain model

[ds-crehm]

Tested with the provided Insomnia collection. Works for me.
Sorting and filtering works only with assetID and creationDate of the asset. Sorting and filtering for the user will be handled in the frontend story #421