You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We had problems with notifcations that are republished by GCs and also have set cache="false".
In these cases, it is not possible to determine who republished the notification via the download link value. In the event of notification format errors, no suitable contact person can be found.
Initial value could be center-id of the originator and then be replaced by the GCs with their center-id.
If we always carry this value with us, we can also determine which GCs republished which origin notification. This could be a useful information in the pre-operational phase.
To be discussed during our next TT-WISMD meeting if useful/needed...
The text was updated successfully, but these errors were encountered:
We had problems with notifcations that are republished by GCs and also have set cache="false".
In these cases, it is not possible to determine who republished the notification via the download link value. In the event of notification format errors, no suitable contact person can be found.
Initial value could be center-id of the originator and then be replaced by the GCs with their center-id.
If we always carry this value with us, we can also determine which GCs republished which origin notification. This could be a useful information in the pre-operational phase.
To be discussed during our next TT-WISMD meeting if useful/needed...
The text was updated successfully, but these errors were encountered: