Forwarding of alerts / investigation within Trace-X upwards and downwards

[mkanal]

Link

• Related to TraceX - alerts / investigation cannot be forwarded within trace-X but new ones have to be set up (tiresome) sig-release#385
• Forwarding of notifications #660

Requirements

• Trace-X should support forwarding of notifications in both directions over more tier levels respecting data sovereignty
• Forwarding has to be acknowledged on each forwarding tier level
• Responses for notifications should be forwards as well (acknowledge is required on tier level)

Questions/Considerations

As Trace-X MUST be interoperable with other solutions, this functionality might be standardized
Invitation of companies which are not C-X members (via email) should be a separate story.

Contribution by

@wiegerterik

[mkanal]

@wiegerterik @jzbmw @ds-crehm fyi

[mkanal]

Concept is done.
Screenshots could be provided by Cofinity-X to gather some feedback.
Topic: Provisioning of Frontend with C-X UX Style conformity.

[felixschmidtcofinity]

Hey all, here our designs for forwarding notifications:

• Alerts
  
• Investigations
  

Feel free to give some feedback.

[mkanal]

Hi @felixschmidtcofinity
you will get feedback on this until Open Meeting on 4.4.2024 is that sufficiant for you?

[mkanal]

@jzbmw @ds-crehm
C-X styled mockup is required to follow the C-X styleguide before integrating this feature.
A C-X design is required for these dialogs.

[jzbmw]

11.04.2024 Open Meeting Discussion:

• Forwarding functionality will be contributed when the current state of the project has been migrated to the current system ( roughly expected to be ready in around 4 weeks)
• minimal efforts done on FE
• Currently it is about just adding one button and two pop-up window's for forwarding

[mkanal]

@felixschmidtcofinity @rogocof
Please take a look here https://github.com/eclipse-tractusx/item-relationship-service/issues/553
We have now had this conceptual alignment in the team.
There are some questions regarding the implementation:

• When a notification is forwarded, the part on which the affected part changes. How is this currently realized?
• how is the relationship between notifications modeled in the database, and how is this connection between notification and forwarded notification used in the application?

[rogocof]

Hi Martin,
Q1: the flow for forwarding investigations and alert is quite different:

• Investigation: After the click on "Forward investigation" the user needs to select the affected part for which the forwarded investigation should be created. Description and severity is copied from original alert but can be edited. Data souvereignity disclaimer is also clearly visible to the user. (see @felixschmidtcofinity screenshots)
• Alerts: Here we need to replace the affected part with the own (parent) part. I did a short draft how this flow looks like:
  

Q2:
It is a pure UI/UX enhancement to "prefill" data from existing notification and forward these. There was no state change or other flag in data model implemented. From data model perspective it is a complete "new" investigation/alert.

@mkanal Does this answers your questions?