-
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] Quality notifications to multiple BPNs #849
[Concept] Quality notifications to multiple BPNs #849
Comments
After alignment with @ds-mwesener: Further discussion needed to find an optimal solution. Choice between the current approach and the approach from #774 still open. |
After a discussion with @mkanal, @jzbmw and @ds-mwesener we decided to follow through with this concept with some modifications. Concept was updated accordingly. Additionally, the suggestions to change the data model will be moved to the story #831 to keep the scope for this ticket clear. |
Not possible to test. |
…ultiple-bpns chore(concept): #849 create concept
PO acceptance in behalf of @jzbmw. Works as intended. |
As user,
I want to be able to send notifications to multiple BPNs,
so that I don't have to create notifications for each BPN individually.
Hints / Details
In #774 a concept to handle messages to multiple BPNs was created. This was based on the current data model and how the creation and sending of notifications and messages work currently in Trace-X. Currently, when multiple parts with with different BPNs are selected, multiple messages (1 per bpn) within one notification are created.
Instead, when multiple parts with different BPNs are selected, separate notifications should be created for each one.
For this, the data model must be changed.
To have a clear vision of this functionality, a concept must be created.
Acceptance Criteria
Backend PBI: #899
Frontend PBI: #900
Out of Scope
The text was updated successfully, but these errors were encountered: