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

[Concept] Handle messages sent to multiple BPNs in the notification message history #774

Closed
2 tasks
ds-crehm opened this issue Mar 21, 2024 · 1 comment · Fixed by catenax-ng/tx-traceability-foss#1164
Assignees
Labels
concept issues describing to work on a concept spillover temporary label for spill over

Comments

@ds-crehm
Copy link
Contributor

ds-crehm commented Mar 21, 2024

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

  • Concept created
  • PBIs created

Out of Scope

  • ...
@ds-crehm
Copy link
Contributor Author

Created the concept.
Decision to do it differently: Not one notification with messages to multiple BPNs -> Multiple notifications created for each BPN
Since data model needs to be changed and several situations are still unclear, a new concept is needed.
-> #849

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
concept issues describing to work on a concept spillover temporary label for spill over
Projects
Status: done
Development

Successfully merging a pull request may close this issue.

2 participants