This commit is contained in:
@@ -94,12 +94,21 @@ By default AyaNova will fill this field in with your email address if it's set i
|
||||
|
||||
### Tags
|
||||
|
||||
Here you can select one or more [Tags](ay-start-form-tags.md) (if the event is related to a taggable object) to act as a filter to include or exclude specific objects. For example, you could create a subscription to the Object Created event, select the type as Customer and the Tag as "residential". That way any Customer created and saved with the Tag "residential" will trigger a notification to you but if a Customer is created without the tag "residential" you will not be alerted.
|
||||
Here you can *filter* by selecting one or more [Tags](ay-start-form-tags.md) (if the event is related to a taggable object) to include or exclude specific objects. For example, you could create a subscription to the Object Created event, select the type as Customer and the Tag as "residential". That way any Customer created and saved with the Tag "residential" will trigger a notification to you but if a Customer is created without the tag "residential" you will not be alerted.
|
||||
|
||||
**All** the tags selected in the subscription are required to be on the object at the moment it is saved / updated / deleted in order to match the subscription requirements and trigger notification. If other tags are on the object besides the ones related to this filter they have no effect on the notification filter.
|
||||
|
||||
If no tags are selected then tags are not considered at all when processing notifications.
|
||||
|
||||
#### Work orders / Quotes / PM and tags
|
||||
|
||||
Most work order descendant object 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.
|
||||
|
||||
|
||||
## Events are triggered when...
|
||||
|
||||
### Business object edited
|
||||
@@ -145,7 +154,7 @@ There are no settings adjustable for in app General notifications.
|
||||
| NotifyHealthCheck | Automatic daily "ping" notification to confirm notification and Generator system is active at server |
|
||||
| BackupStatus | Result of last Backup operation at server |
|
||||
| CustomerServiceReminder | Scheduled service date / time is about to be reached. (Customer or HeadOffice type users only) |
|
||||
| WorkorderTotalExceedsThreshold | The balance of a Work order has exceeded a threshold (the "Andy") |
|
||||
| WorkorderTotalExceedsThreshold | The balance of a Work order has exceeded a threshold and is set to completed status (the "Andy") |
|
||||
| WorkorderStatusAge | A Workorder has been sitting at the selected status for longer than the selected time frame |
|
||||
| UnitWarrantyExpiry | A Unit's warranty expiration date is reached |
|
||||
| UnitMeterReadingMultipleExceeded | A meter reading has a difference from the last reading by the selected amount (negative OR positive to cover count _down_ meters or rollover / reset meters, can tag filter by Unit tag) |
|
||||
@@ -155,19 +164,5 @@ There are no settings adjustable for in app General notifications.
|
||||
| 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.
|
||||
|
||||
@@ -141,3 +141,8 @@ As some Work order data is not shown or available to restricted Users, several f
|
||||
|
||||
Some objects contain a "Price override" field to allow for manually adjusting the price to an arbitrary value. This override supersedes any other source for the price including Contracts and / or the source object's price itself. Contract adjusted pricing is not part of the Manual Price Override feature; only values entered manually on the work order form in the "Price override" field will be present in that field.
|
||||
|
||||
### NOtifications tips
|
||||
- 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.
|
||||
Reference in New Issue
Block a user