Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compliance GX Tagus Release V2 Api | Integrate the Gaia-X Clearinghouse Interface #1217

Open
1 of 2 tasks
tfjanjua opened this issue Dec 27, 2024 · 1 comment
Open
1 of 2 tasks
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@tfjanjua
Copy link
Contributor

tfjanjua commented Dec 27, 2024

Description

Integrate the V2 api from Gaia-X Tagus release in company onboarding and SD document creation.

Gaia-X has released the V2 api in Tagus release which have changes in request and response interfaces.
So portal backend have to adapt these new changes.

This new version have more flexibility from Gaia-X perspective and Portal BE must switch to new api for correct data validation for companies onboarding and Sd document creation.

Currently Portal BE is using V1 api from Gaia-X

Acceptance Criteria

  • Portal backend would need to analyse the V2 api from Gaia-X and then integrate the changes in backend code for new interfaces.
  • Company onboarding should be successful by using V2 api from clearing house.

Test Cases

There would be no change in existing flow of company onboarding because its an update of clearing house api version so, existing test cases should run successfully. There are probably some changes of interfaces in the existing test cases.

Corresponding Release Ticket

eclipse-tractusx/sig-release#993

@tfjanjua tfjanjua added the enhancement New feature or request label Dec 27, 2024
@tfjanjua tfjanjua added this to the Release 25.03 milestone Dec 27, 2024
@tfjanjua tfjanjua self-assigned this Dec 27, 2024
@tfjanjua tfjanjua added this to Portal Dec 27, 2024
@github-project-automation github-project-automation bot moved this to NEW USER REQUEST in Portal Dec 27, 2024
@tfjanjua tfjanjua moved this from NEW USER REQUEST to IN PROGRESS in Portal Dec 27, 2024
@dorkabcox
Copy link

dorkabcox commented Jan 16, 2025

From Cofinity-X side we agree the strictness levels/"validationMode" is the ideal way to go with, however there are instances where complete override might still be necessary. We would like the option to be there, and not use it unless absolutely needed.
Regarding manual validation in case automated process fails, further refinement of the process will take place on the 23rd January among Cofinity-X and the GXDCH provider, of which we'll provide update.

One example for clear necessity recently: Issue in the formatting of the legal entity identifiers / spelling errors

thyssenkrupp Automotive Systems GmbH - spelling
While the provided commercial registration number, HRB 19873, is indeed valid, it is associated with an organization called ThyssenKrupp Automotive Systems GmbH, which was also seen on the screenshot of the German Commercial Register provided. While it was all clear that these both refer to the same legal entity and the difference is minimal (T and K being uppercase), Clearing House requires a strict match to claim the legal entity is valid.

Please let me know if further info is desired! :) @evegufy @MaximilianHauer

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: IN PROGRESS
Development

No branches or pull requests

2 participants