[TRACE-X] Make the part & notification information more user friendly

[rogocof]

Overview

As a User I want to see the most important information of a part or notification as easy as possible.

Explain the topic in 2 sentences

The current information provided for even one part or notification is overwhelming for the user. That is why we want to restructure the provided information.

What's the benefit?

See only important information first. Hide or relocate not important data of a certain part.

What are the Risks/Dependencies ?

--

Detailed explanation

The parts/notification table and the detail view of a part have to many different information to be shown! This overwhelms the user and needs to be reduced and restructured.

Current implementation

Every possible information for a certain part is displayed in parts table and in the detail view.

Proposed improvements

• Reduce the default set of displayed columns in parts table (can still be configured manually of course).
• On parts detail view: Show only business related data like customerPartId, manufacturerPartId, productionDate etc. in a more prominent way and relocate the more technical information like importState or semanticModelId
• Ease the access of a certain part or notification with UX best practices. Access per click instead of three dots.
• Give the user an in-app notification if a new notification was received

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)