This type of notification is subscribed via the visualization and is completely free. The configuration of push notifications is done in the Explorer Messages.
When allowing notifications in the visualization, a key (Push Endpoint) is created via the Internet with the corresponding Push service. This is then saved under the respective User. Subsequently, these can be managed under the context menu Project
User Management
Users
Push Endpoints.
On each subsequent visit to the visualization, the current key is automatically transmitted to the server and updated if necessary.
When a push message is sent, it is first delivered to the last active Push endpoint. This minimizes the response time for unreachable (dead) endpoints. Expired or invalid endpoints are automatically removed when sending in case of an error.
Notes:
To receive notifications in the desktop browser, the browser must be open.
If the endpoint temporarily has no Internet connection, delivery may be delayed by up to 24 hours.
In Core 1, only meta keys are transmitted. These can only be received if the endpoint actively establishes a connection to the server. From Core 2 and higher, complete messages including content (except images) are directly transmitted to the Push endpoint. This ensures reliable reception even without an active server connection.
In the individual groups, further conditions for the notification can be stored. Currently, it is only possible to distinguish between desktop and mobile device. Panels do not support push messages.
It is possible to display a webcam or an image via the push notification. For this purpose, the first image of the file attachment is used. This must be of type JPEG, PNG, or GIF. Also note that the License for using File Attachments is available.
Currently, a unique ID per project is used for Push registration. This means that only one Service Worker (background program of the website) with push notifications is provided per device.