You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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
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
The text was updated successfully, but these errors were encountered: