admin/raven
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Browse Source
This commit is contained in:
John Cardinal
2022-02-10 00:46:48 +00:00
parent 71fe407b7e
commit f5ed5e291f
3 changed files with 72 additions and 50 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
docs/8.0/ayanova/docs/home-notifications.md
View File

@@ -1,27 +1,33 @@
# Notifications
This form shows notifications received in the last 90 days, for [notification subscriptions](home-notify-subscriptions.md) to events of interest that happen in AyaNova and are set to deliver "in app" rather than by email or other means of delivery.
This form shows notifications received in the last 90 days that are set to deliver "in app" rather than by email or other means of delivery.
## Authorization Roles required
Notifications are available to _all_ users of AyaNova regardless of their [roles](ay-biz-admin-roles.md).
In app notifications are available to _all_ users of AyaNova regardless of their [roles](ay-biz-admin-roles.md).
## How to access in-app notifications
The bell icon in the [App bar](ay-start-form-overview.md#app-bar) at the top of AyaNova is used to open the in-app notifications list.
The bell icon will change color and show a small number beside it indicating that new unseen notifications are available and the number of new notifications.
The bell icon will change color when new notifications arrive and show a number badge beside it indicating the number of new unseen notifications that are in the list.
## How the in app notification works
Notifications are generated for both events that the user has [subscribed to](home-notify-subscriptions.md) as well as general system notifications specific to the user such as certain types of errors or general events built into AyaNova. When a notifiable event takes place at the server, the server will check for any Users that have a subscription that matches the event and will deliver that notification according to the subscription delivery method. For in-app type notifications this means they will be placed in a table in the database for the web app to pick up on it's next check for notifications.
Notifications are generated for both events that the user has [subscribed to](home-notify-subscriptions.md) as well as general system notifications specific to the user such as certain types of errors or general events built into AyaNova.
When a notifiable event takes place at the server, the server will check for any Users that have a subscription that matches the event and will deliver that notification according to the subscription delivery method.
For in-app type notifications this means they will be placed in a table in the database for the web app to pick up on it's next check for notifications.
The AyaNova web application checks for notifications by contacting the AyaNova server periodically on a cycle as follows:
- Immediate check just after login
- Every 60 seconds while logged in
If the web application can't contact the server during a check (for example if a cell signal has cut out temporarily), it will automatically slow down the frequencey of checks by a factor of 1.5 up to a maximum delay of half an hour. This is to preserve battery life on a device by not checking as frequently when there is no signal available. Once contact is made then the cycle goes back to 60 seconds.
If the web application can't contact the server during a check (for example if a cell signal has cut out temporarily), it will automatically slow down the frequencey of checks by a factor of 1.5 up to a maximum delay of half an hour.
This is done to preserve battery life on a device by not checking as frequently when there is no signal available. Once contact is made then the cycle goes back to 60 seconds.
If you are awaiting a notification and know you had a bad network connection and it has been restored, refreshing the browser page will reset the cycle back to 60 seconds and check immediately for notifications.
@@ -29,7 +35,9 @@ Due to this built in delay in checking it's possible that a notifiable event can
When a notification has been fetched for display by opening the notifications form it will be flagged as having been seen and the "badge" beside the bell icon showing new notifications will vanish until more new notifications are received.
In-app notifications are meant to be temporary and are only kept for 90 days then automatically deleted by the AyaNova server after which time they will no longer appear in this notifications form. If you require a permanent record of some notifications we recommend creating a duplicate [notification subscription](home-notify-subscriptions.md) with delivery via email so they can be kept in the email application itself.
In-app notifications are meant to be temporary and are only kept for 90 days then automatically deleted by the AyaNova server after which time they will no longer appear in this notifications form.
If you require a permanent record of some notifications we recommend creating a duplicate [notification subscription](home-notify-subscriptions.md) with delivery via email so they can be kept in the email application itself.
You can also delete notifications if desired but it's not necessary to do so.
@@ -55,7 +63,9 @@ Open button is used to open the notification subscription itself. This is handy
#### Direct notification
This menu option opens the [direct notification](home-notify-direct.md) where you can send a notification directly to one or more Users in AyaNova. This is separate from the [Memo](home-memos.md) system which is more like sending an email.
This menu option opens the [direct notification](home-notify-direct.md) form where you can send a notification directly to one or more Users in AyaNova.
This is separate from the [Memo](home-memos.md) system which is more like sending an email.
Direct notification is for quickly sending a short message to other users that will appear in their in app notifications form as a "General notification".