Better Support of Legal Names and Identifiers

[ybidois]

Feature Summary

The Portal registration flow and its overall UX and UI must be compatible with our customers' legal names and identifiers.

Change Description

Business Value and Requirements

Allow all customers to register smoothly with both their legal names and identifiers:

• Have legal name used only where it is needed

• Use short name everywhere else

• Clear support and validation patterns for legal identifiers

• Great UX/UI integration

High-Level Overview

• Review the use of legal and short names across the portal and modify them according to business requirements

• Modify all form fields to match both legal and short name requirements

• Improve UX/UI for legal and short names

• Support and validate the legal identifiers based on the Gaia-X Digital Clearing House list

Detailed Analysis

• Customer registration:

  • Allow the use of any legal name based on country specificity

  • Allow the choice of a short name with limited characters

  • Allow the use of legal identifiers as per the Gaia-X Clearing House list

• Use the brand name in all subsequent fields, unless the legal name is required

• Where the legal name is required, adjust the UI

• Where the short name can be used, adjust the UI

• For each supported legal identifier, have the correct validation rules (REGEX)

Impacted Components

• BPDM can process all legal names and has no restrictions or REGEX in place

Acceptance Criteria

• Portal should support countries as per the Catena-X official White List (+ Yellow List under certain conditions).

• 100% of all legal names in the countries we officially support are accepted in the registration process

  • Very long names

  • Country-specific with unique characters

• Legal names are used only where required, brand names are otherwise used

• Legal identifiers should match the Gaia-X Clearing House official list

• OSP functionality should also comply with the defined requirements

Test Scenarios

• For each supported country, successful registration of an edge case legal name (very long or special characters) + identifier

• Use of short name across:

  • Registration process

  • User invitation process

  • Company detail pages

  • App release process

  • Service release process

Risks/Dependencies

• Gaia-X Clearing House

Issues

eclipse-tractusx/portal-frontend#993
eclipse-tractusx/portal-frontend#1007

[stephanbcbauer]

@ybidois not sure about this feature. Is it planned to present it in tomorrow's planning? It was never presented in a Refinement meeting. Did we miss something?

[Sebastian-Wurm]

• Regarding identifier types, we have an overlap with Harmonization and Enhancement of identifier types #605. Let's work together here.
  • We probably want to store the REGEX in BPDM rather than in the Portal. @nicoprow: Please confirm.
  • Regarding GXDCH identifier types, there is a first implementation proposal for portal-backend here: Add new BPDM identifier types portal-backend#895
• Regarding "brand name": please use the term "short name" from BPDM as defined in CX-0012.

[nicoprow]

• Regarding identifier types, we have an overlap with Harmonization and Enhancement of identifier types #605. Let's work together here.

  * We probably want to store the REGEX in BPDM rather than in the Portal. @nicoprow: Please confirm.
  * Regarding GXDCH identifier types, there is a first implementation proposal for portal-backend here: [Add new BPDM identifier types portal-backend#895](https://github.com/eclipse-tractusx/portal-backend/issues/895)
  

  • Regarding "brand name": please use the term "short name" from BPDM as defined in CX-0012.

Any validation on the identifier types eventually also needs to be performed in the Pool. Yea we will need to align on the REGEX and we can also make it available over the BPDM API to reduce duplication and reduce the risk of mismatched validations.

[ybidois]

Hi @Sebastian-Wurm, @nicoprow, I agree with what you propose:

• Using the short name → I updated the feature description accordingly
• Aligning on REGEX, storing in BPDM, and making it available over BPDM API
  It will reduce a lot of errors on all sides.

Let me check with @evegufy and the Open-Source Portal team the best way to work together on this and we will get back to you.