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-01-27 22:28:33 +00:00
parent 90b26359db
commit 1ecae5cabe
2 changed files with 28 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -1,25 +1,16 @@
# NOTIFICATIONS
# Notifications
[under construction]
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.
#b4beta (complete this and add ss)
## Authorization Roles required
This form shows "in app" notifications received in the last 90 days.
Notifications are kept for 90 days then automatically deleted.
Notifications are available to _all_ users of AyaNova regardless of their [roles](ay-biz-admin-roles.md).
TODO: Notes for docs / items to cover
- TAG changes on work order header and Workorder related notifications for *descendants* on work orders.
Most work order descendant notifications will use the Work order header tags for comparison with their notification setting with the exception of descendants that have their own Tags (Work order items and Work order item Units are currently the only descendants with their own tags).
## How to access in-app notifications
For all other descendants, they will process notifications and filter by tag against the work order header tags in place at the moment they are saved after creation or update *only*.
The bell icon in the [App bar](ay-start-form-overview.md#app-bar) at the top of every form in AyaNova is used to open the in app notifications list.
Changing the work order header tags on an existing work order does not automatically trigger a re-evaluation of descendant notification items. Only when those descendants themselves are edited and saved will the tags be re-assessed. This means that ideally tags should be set *first* on the work order before any descendant items that might be dependant on certain tags being present.
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.
- WorkOrderExceedsTotal notification ("The Andy") is triggered only when a workorder is set to a "completed" type status and saved.
- TIPS
Workorder status related notification uses:
Completed - Use workorder status change type notification and any status that is of type completed relevant to user to get relevant completed state notification
Completed follow up - follow up with customer after service with a workorder status age type notification on a completed type status and set age value to desired wait time to follow up.
In-app notifications are meant to be temporary and are only kept for 90 days then automatically deleted by the AyaNova server. 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.

20
docs/8.0/ayanova/docs/home-notify-subscriptions.md
View File

@@ -110,3 +110,23 @@ There are no settings adjustable for in app General notifications, however Users
| QuoteStatusAge | A Quote has been sitting at the selected status for longer than the selected time frame |
| CopyOfCustomerNotification | Copy of any notification sent to Customer for AyaNova User. Filterable by Customer Tag |
| WorkorderCreatedForCustomer | Customer notification sent when a service type work order is created for them (or if HeadOffice Contact user, one of their Customers) |
00000000000000000000000000000000000000000000000000000000000000000000000000
TODO: Notes for docs / items to cover
- TAG changes on work order header and Workorder related notifications for _descendants_ on work orders.
Most work order descendant notifications will use the Work order header tags for comparison with their notification setting with the exception of descendants that have their own Tags (Work order items and Work order item Units are currently the only descendants with their own tags).
For all other descendants, they will process notifications and filter by tag against the work order header tags in place at the moment they are saved after creation or update _only_.
Changing the work order header tags on an existing work order does not automatically trigger a re-evaluation of descendant notification items. Only when those descendants themselves are edited and saved will the tags be re-assessed. This means that ideally tags should be set _first_ on the work order before any descendant items that might be dependant on certain tags being present.
- WorkOrderExceedsTotal notification ("The Andy") is triggered only when a workorder is set to a "completed" type status and saved.
- TIPS
Workorder status related notification uses:
Completed - Use workorder status change type notification and any status that is of type completed relevant to user to get relevant completed state notification
Completed follow up - follow up with customer after service with a workorder status age type notification on a completed type status and set age value to desired wait time to follow up.