1.7 KiB
NOTIFICATIONS
[DOCUMENTATION UNDER CONSTRUCTION]
This form shows "in app" notifications received in the last 90 days. Notifications are kept for 90 days then automatically deleted.
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.