Forwarding of notifications #660
-
During work on #436 I noticed that there is an open ticket about the possibility to forward notifications: eclipse-tractusx/sig-release#385 It should be possible to forward a notification multiple times to multiple partners. This makes it very difficult to keep track of all of the information consistently within a single notification. My idea is to create duplicates of the initial notification each time it is forwarded. The duplicated notification can then be handled independently and contain all relevant information. The initial notification will remain in the state "Forwarded". Maybe this helps with the implementation of eclipse-tractusx/sig-release#385 Thank you! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
I agree that there should be duplicates of the original request. In fact, I think it is mandatory, because in some cases it might be necessary to share different information. Just a comment on your visualisation. I would suggest that we don't synchronise the status "Forwarded", or at least let the user decide if that's what they want. As far as I understand, there might be cases where a supplier doesn't want to inform his customer if the notification is forwarded. |
Beta Was this translation helpful? Give feedback.
I agree that there should be duplicates of the original request. In fact, I think it is mandatory, because in some cases it might be necessary to share different information.
Just a comment on your visualisation. I would suggest that we don't synchronise the status "Forwarded", or at least let the user decide if that's what they want. As far as I understand, there might be cases where a supplier doesn't want to inform his customer if the notification is forwarded.