[TRACE-X] Show & Export relationships between own parts and supplier parts on parts page

[rogocof]

Overview

As a User I want to easily see and process child parts already on parts overview table (parts page) in order to get an overview of the relationship without going to the detail page.

Explain the topic in 2 sentences

We need an easy way to give the user the opportunity to see parent-child-relationships for more than one part. It would also be very nice to export this view in a format like csv to give the user the option to process this data further in other tools or systems.

What's the benefit?

• Overview of relationships without clicking to much.
• Easy export for part / relationship reports

What are the Risks/Dependencies ?

No breaking changes expected. Performance of the loading of child parts is to be considered.

Detailed explanation

Currently it is hard to see relationships of more than one (parent) part. For seeing a direct relationship it is necessary to jump on the detail page of each part and even then it is visualized only as tree. This makes it really hard for the user to trace down parts when applying certain filter criteria on the parts table.

Current implementation

Relationships are only shown in the detail view as tree visualization.

Proposed improvements

• Make each row of the parts table collapsable. If the row is extended you see a first set of child parts with the option to load more.
• Create an export of the current state of the table incl. all child parts which are extended
• Show a full table of child and parent parts in the detail view of each parts as an alternative to the tree visualization

Feature Team

Cofinity-X

Contributor

• @rogocof
• @mkanal
• UX-Design:
  @Cofinity-UX
  @sophiepotyka

Committer

• @mkanal
• @ds-mwesener
• @ds-lcapellino

User Stories

• Issue 1, linked to specific repository
• Issue 2, linked to another specific repository

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.

In the context of the standards 126 and 127, typically only one is applicable, depending on the specific use case. Please cross out one of the two standards that does not apply.

• 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)
    • CX-0126 Industry Core: Part Type 2.0.0
    • CX-0127 Industry Core: Part Instance 2.0.0
  • 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)