Block Notifications

[max-wies-cofinity]

As a User of a Supplier,
I want to send block notifications with additional logistics information for parts that must no longer be used by the customer,
so that the customer immediately receives information about blocked parts and can take appropriate action based on clearly defined status models.

Hints / Details

• In this feature, we extend the reference implementation to support block notifications, as introduced in the Traceability Kit, enabling suppliers to notify customers about parts that should no longer be used.

• The users of a supplier can create a notification using a specialized “Block Notification” type.

• The affected parts (digital twins) and the required logistic data (such as componentLevelContainment, periodAndVolumeLevelContainment, and locationInTheContainer) will be uploaded through a defined file format (since no aspect model is currently defined, this information must be provided by the users; however, manual input through a form dialog would be too cumbersome).

• The system performs high-level validation of the uploaded data to ensure that all mandatory fields are provided.

• The notification flow will leverage standard state models as defined in the specification—using states at the notification level (e.g., Created, Sent) and at the individual part level (e.g., Active, Blocked, Cancelled).

Acceptance Criteria

• The supplier can upload a list with block information and create a block notification.

• The customer sees block notifications in the received notifications view.

• The customer can respond with a block status of "PART_BLOCKED" or "CANCELED".

• The supplier receives status updates when a part is blocked and can also send updates when an ACTIVE block status is cancelled.

• All block information for a part is managed in the detail view of this block notification.

• Block Notifications are added to the dashboard view.

[rogocof]

to be postponed @max-wies-cofinity @mkanal