Registration Process Improvements

[ybidois]

Overview

Explain the topic in 2 sentences

Improve the registration process based on our learnings as CX-Operator

What's the benefit?

Make registration process easier and faster

What are the Risks/Dependencies ?

BPDM and Gaia-X Clearing House

Detailed explanation

Current implementation

Current registration process includes steps we don't need and registration data cannot be modified once submitted. The registration process should also be improved when it comes to data exchange with BPDM and Gaia-X Clearing House.

Proposed improvements

• Change Document Upload Requirements in Registration Process → As agreed with Catena-X Board, the Document Upload is required only for OSPs during Registration process. Other roles don't need it anymore.
• Ability to retrigger/correct company registration
• Set Catena-X Membership Flag during Registration process
• Pre-fill fields with BPDM data (identifiers, region names, etc.)
• Send registration data inputed by customers to BPDM, in case of BPN pre-fill

Feature Team

Contributor

• @dhiren-singh-007
• @shubhamv-ss
• @Usmanfee
• @ybidois

Committer

User Stories

• https://github.com/eclipse-tractusx/portal-backend/issues/1111

Acceptance Criteria

• [ ] Criteria 1
• [ ] Criteria 2
• [ ] Criteria 3

Test Cases

Test Case 1

Steps

1. Do something
2. Click something
3. Add something

Expected Result

1. Expectation
2. Expectation
3. Expectation

Architectural Relevance

The following items are ensured (answer: yes) after this issue is implemented:

• [ ] This feature aligns with our current architectural guidelines
  • Data Sovereignty: All data sharing activities across company boundaries follow the Catena-X Regulatory Framework, in particular the Data Exchange Governance, and the Dataspace Protocol via a compliant Connector (like the tractusx-edc or similar, see Connector KIT)
  • [ ] CX-0010 Business Partner Number
  • [ ] CX-0013 Identity of Member Companies
  • [ ] CX-0018 Data Space Connectivity (EDC)
  • [ ] CX-0049 DID Document Schema
  • [ ] CX-0050 Framework Agreement Credential
  • [ ] CX-0149 Verified Company Identity
  • Interoperability: Digital Twins are used (compliant to the Digital Twin KIT and the Industry Core KIT)
  • [ ] CX-0001 EDC Discovery API
  • [ ] CX-0002 Digital Twins in Catena-X
  • [ ] CX-0018 Data Space Connectivity (EDC)
  • Data Format:
  • [ ] The data model is based on a published Semantic Model
• [ ] The impact on the overall system architecture has been assessed. The Feature does not require changes to the architecture or any existing standard? Please have a look here on the overarching architecture
• [ ] Potential risks or conflicts with existing architecture has been assessed

Justification: (Fill this out, if at least one of the checkboxes above cannot be ticked. Contact the Architecture Management Committee to get an approval for the justification)

Additional information

• [ ] I am aware that my request may not be developed if no developer can be found for it. I'll try to contribute a developer (bring your own developer)

[ybidois]

Take into account https://github.com/eclipse-tractusx/sig-release/issues/605

[stephanbcbauer]

Some hints from Release Management (@ther3sa) and Tractus-X Project Lead (@stephanbcbauer)

• Status currently in Inbox. ⇾ Only features with status backlog are considered in open planning
• Please add missing sections from the feature template, or fill them out
• Please add committer

[evegufy]

Committers: @oyo @ntruchsess @Phil91 @evegufy