Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Traceability KIT 24.12] Block Notification #1028

Draft
wants to merge 51 commits into
base: main
Choose a base branch
from

Conversation

johannsvarela
Copy link
Contributor

@johannsvarela johannsvarela commented Sep 9, 2024

Description

This PR updates the sections below with content of the new block notification for the upcoming release 24.12. For detailed information regarding the changes made have a look at the updated changelog file.

  • Business View
  • Architecture View
  • Development View

Related Issues

Fixes eclipse-tractusx/sig-release#782 / https://github.com/catenax-eV/sig-roadmap/issues/17

Pre-review checks

Please ensure to do as many of the following checks as possible, before asking for committer review:

@stephanbcbauer
Copy link
Member

@johannsvarela i think the title of this PR could be renamed? 24.08 -> 24.12

@johannsvarela johannsvarela changed the title [Traceability KIT 24.08] Block Notification [Traceability KIT 24.12] Block Notification Oct 14, 2024
> :raised_hand: For the current release, **version 1.2.1 is mandatory** and must be supported by every App provider. The newer version 2.0.0 can be supported optionally.

## Block Notifications
While quality notifications are primarily aimed at (first) contact between business partners (e.g. to initiate a supplier self-assessment), block notifications represent an extended form of data exchange in order to actively initiate an immediate measure to block or sort out the produced parts at the customer's production or logistics. As the quality notifications, block notifications take place between traceability applications or other application stacks, so that this functionality must be implemented by both busniess partners application. However, block notifications include a different status model and, in particular, other information that is critical to the customer's blocking process.
Copy link

@SteDue SteDue Oct 15, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

note:

  • check if the info in brackets is really needed --> (e.g. to initiate a supplier self-assessment)
  • typo: ... by both business partners application ...
  • "and, in particular, other information that is critical to the customer's blocking process." --> better:
    "and, in particular, additional information that is critical to the customer's blocking process."

Below the sequence for sending, updating and resolving of notifications between (traceability) applications is shown with UML sequence diagrams. In all cases, Http POST requests are used. Those Http endpoints are described in the section (TRS) Quality Notification Endpoints and EDC Contract Offerings.
**Scenario 1:** In this case, it is assumed that the sender sends a list of parts with the associated block information to the recipient. The block status of each part is set to ACTIVE by default.

When all block information has been received by the recipient, checked internally, further processed and finally all affected parts were blocked or sorted out, this information is sent back to the sender through a status update (PART_BLOCKED).
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we add that the back information is optional?

@johannsvarela johannsvarela self-assigned this Oct 17, 2024
@johannsvarela johannsvarela added the enhancement New feature or request label Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[R24.12] Traceability KIT Adaptation: Notifications Extension: Block-notification
3 participants