-
Notifications
You must be signed in to change notification settings - Fork 23
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
[Concept] Handle messages sent to multiple BPNs in the notification message history #774
Closed
2 tasks
Comments
1 task
10 tasks
2 tasks
Created the concept. |
2 tasks
ds-mmaul
pushed a commit
that referenced
this issue
Apr 15, 2024
ds-mmaul
pushed a commit
that referenced
this issue
Apr 15, 2024
ds-mmaul
pushed a commit
that referenced
this issue
Apr 15, 2024
ds-mmaul
pushed a commit
that referenced
this issue
Apr 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As user,
I want to see what happens when I send a notification to different BPNs,
so that I can take appropriate actions and know what is happening with my notification.
Links
Hints / Details
Multiple assets can be selected and a notification can be created for them. Since assets can come from different BPNs, the notification may be sent to multiple BPNs. However, in our message history, we currently only show one message to a single BPN.
The field "sendTo" (BE) / "Sent to BPN" (FE) is obsolete as the BPN can be different for each message.
Similarly, when creating a quality alert the user may not input a receiver BPN anymore, as the BPN can be taken from the chosen assets directly and there's no need for a manual input anymore.
Acceptance Criteria
Out of Scope
The text was updated successfully, but these errors were encountered: