You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As Trace-X I want forwarding of notifications in case of alerts and notifications so that a quality incident could be forwarded app supported through the supply chain respecting the data sov
Acceptance Criteria
Concept created of handling forwarded notification
Supporting forward of quality notifications over the trace-x frontend
Received quality investigation could be forwarded to customer or supplier respecting the direction the incident was reported in the supply chain (upwards / downwards)
Meta information from inital quality notifications are used for the forwarded quality notifications
Meta information of forwarded notifications could be overridden by supervisor
Forwarding notification requires role supervisor
In case of forwarding notification based on affected part of customer, a new selection of affected part for supplier must be possible. OEM reports on a gearbox of a vehicle - the gear is the affected part of the forwarded notification.
User is able to comprehend the relationship between received notification (OEM) and forwarded notification (Supplier)
In case the supplier accepts or declines a forwarded notification, this could be forwarded via the initial notification received from OEM level
The app persists and visualize the relationship between notifications and forwarded notifications this relationship could be used to report back information of forwarded messages from tier levels
As Trace-X
I want forwarding of notifications in case of alerts and notifications
so that a quality incident could be forwarded app supported through the supply chain respecting the data sov
Acceptance Criteria
NFR
Hints / Details
Out of Scope
The text was updated successfully, but these errors were encountered: