-
Notifications
You must be signed in to change notification settings - Fork 86
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
johannsvarela
wants to merge
51
commits into
eclipse-tractusx:main
Choose a base branch
from
johannsvarela:docs-kits/trace-block-notification-release-24.12
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
[Traceability KIT 24.12] Block Notification #1028
johannsvarela
wants to merge
51
commits into
eclipse-tractusx:main
from
johannsvarela:docs-kits/trace-block-notification-release-24.12
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ication-release-24.12
@johannsvarela i think the title of this PR could be renamed? 24.08 -> 24.12 |
johannsvarela
changed the title
[Traceability KIT 24.08] Block Notification
[Traceability KIT 24.12] Block Notification
Oct 14, 2024
…ication-release-24.12
SteDue
reviewed
Oct 15, 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. |
There was a problem hiding this comment.
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."
SteDue
reviewed
Oct 15, 2024
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). |
There was a problem hiding this comment.
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?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
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: