diff --git a/docs/8.0/ayanova/docs/customer-notify-subscriptions.md b/docs/8.0/ayanova/docs/customer-notify-subscriptions.md index 874067bc..686f5caa 100644 --- a/docs/8.0/ayanova/docs/customer-notify-subscriptions.md +++ b/docs/8.0/ayanova/docs/customer-notify-subscriptions.md @@ -68,9 +68,9 @@ Only Customers who are set to Active and have an email address set will be notif ### Duplicate or overlapping notifications -You can set up multiple subscriptions for the same event to allow for alternative languages and other settings. Because of this, it is possible to set a combination of settings that could result in the same customer being notified more than once of the same event. +You can set up multiple subscriptions for the same event to allow for alternative languages and other settings. Because of this, it is possible to set a combination of settings that could result in the same customer being notified more than once of the same event. -To prevent redundant excess notifications, AyaNova will only send *one* notification per event to the same Customer. If two notification subscriptions for the same event would apply to the same Customer, the subscription created first (lowest id number) will "win" and be the one used to make the delivery. +To prevent redundant excess notifications, AyaNova will only send _one_ notification per event to the same Customer. If two notification subscriptions for the same event would apply to the same Customer, the subscription created first (lowest id number) will "win" and be the one used to make the delivery. ### Email address @@ -90,16 +90,16 @@ In the case of time delayed notifications they are still created at the moment o The following table shows the types of notification events currently available for Customer notification subscription. -| EVENT | DESCRIPTION | -| ------------------------------- | -------------------------------------------------------------------------------------------------------- | -| Work order status change | Any _change_ of Workorder Status including from no status (new) to a _specific_ selected status ID value | -| CSR accepted | Customer service request accepted | -| CSR rejected | Customer service request rejected | -| Quote status change | Any _change_ of Quote Status including from no status (new) to a _specific_ selected status ID value | -| Work order completed | Service work order is set to any status that is flagged as a "Completed" type of status. | -| Customer service reminder | Scheduled service date / time is about to be reached | -| Workorder status age | A Workorder has been sitting at the selected status for longer than the selected time frame | -| Work order created for customer | Customer notification sent when a service type work order is created for them | +| EVENT | DESCRIPTION | +| ------------------------------- | ---------------------------------------------------------------------------------------------------- | +| Work order status set | Workorder Status set to selected Status value | +| CSR accepted | Customer service request accepted | +| CSR rejected | Customer service request rejected | +| Quote status change | Any _change_ of Quote Status including from no status (new) to a _specific_ selected status ID value | +| Work order completed | Service work order is set to any status that is flagged as a "Completed" type of status. | +| Customer service reminder | Scheduled service date / time is about to be reached | +| Workorder status age | A Workorder has been sitting at the selected status for longer than the selected time frame | +| Work order created for customer | Customer notification sent when a service type work order is created for them | ## Notification subscription list diff --git a/docs/8.0/ayanova/docs/home-notify-subscriptions.md b/docs/8.0/ayanova/docs/home-notify-subscriptions.md index 85a18884..95ca90bb 100644 --- a/docs/8.0/ayanova/docs/home-notify-subscriptions.md +++ b/docs/8.0/ayanova/docs/home-notify-subscriptions.md @@ -151,41 +151,42 @@ The General notification type is a special case, all users are automatically sub There are no settings adjustable for in-app General notifications, they are built in, however it is possible to create another general notification with email delivery. -## Notification event types +## Notification event types and triggers -The following table shows the types of notification events currently available for subscription. +The following table shows the types of notification events currently available for subscription. Note that not all event types will work for all users depending upon the roles and user type involved. +Tag filters will restrict to only objects with those tags triggering notification and are optional unless specified otherwise. When no tags are specified then _all_ objects regardless of tag will be considered for notification. -| EVENT | DESCRIPTION | -| --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Backup status | Result of last automated backup | -| Contract expiring | Contract expiration | -| CSR accepted | Customer service request accepted. (intended for Customer users) | -| CSR rejected | Customer service request rejected. (intended for Customer users) | -| Customer service reminder | Scheduled service date / time is about to be reached. (Customer or HeadOffice type users only) | -| General notification | Any general notification including direct text notifications between users (built in but provided for email alternative delivery) | -| Notify health check | Automatic daily (or any time server is restarted) "ping" notification to confirm notification and Generator system is active at server | -| Object age | Any object, Age (conditional on AgeValue) after creation event of any object of selected specific type and optionally selected tags | -| Object created | Creation of core business object of selected type and tags | -| Object deleted | Deletion of core business object of selected type and tags | -| Object modified | Any changes and saving of core business object of selected type and tags | -| Outside service overdue | Unit sent for 3rd party service is overdue | -| Outside service received | Unit sent for 3rd party service has been received back | -| Part request received | Part requested via a Workorder has been received | -| Preventive Maintenance insufficient inventory | Upcoming P.M. order will not have enough inventory to generate without making a part request | -| Preventive Maintenance stop generating date reached | P.M.'s "Stop generating" date has been reached | -| Preventive Maintenance workorder generation failed | Error generating a work order from a P.M. order | -| Quote status age | A Quote has been sitting at the selected status for longer than the selected time frame | -| Quote status change | Any _change_ of Quote Status including from no status (new) to a _specific_ selected status ID value | -| Reminder imminent | A Reminder is about to reach it's specified start date/time | -| Review imminent | A Review is about to reach it's specified review date/time | -| Scheduled on work order | User is scheduled on (added to) a Work order | -| Scheduled on work order imminent | Scheduled date and time reached for workorder which User is scheduled | -| Server operations problem | Any timely and serious issue related to internal AyaNova Server operations requiring attention | -| Unit meter reading multiple exceeded | A meter reading entry 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) | -| Unit warranty expiry | A Unit's warranty expiration date is reached | -| Work order completed | Service work order is set to any status that is flagged as a "Completed" type of status. (Customer / HeadOffice or staff User notification) | -| Work order completed status overdue | Workorder not set to a "Completed" type Status before the selected duration from created date | -| Work order created for customer | Customer notification sent when a service type work order is created for them (or if HeadOffice Contact user, one of their Customers) | -| Work order status change | Any _change_ of Workorder Status including from no status (new) to a _specific_ selected status ID value | -| Work order total exceeds threshold | The balance of a Work order has exceeded a threshold and is set to completed status (the "Andy") | -| Workorder status age | A Workorder has been sitting at the selected status for longer than the selected time frame | +| EVENT | DESCRIPTION | +| --------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Backup status | Result of last automated backup | +| Contract expiring | Contract expiration date is within selected "Notify before event" | +| CSR accepted | Customer service request accepted. (intended for Customer users) | +| CSR rejected | Customer service request rejected. (intended for Customer users) | +| Customer service reminder | Scheduled service date / time is within "Notify before event" selected. (Customer or HeadOffice type users only) | +| General notification | Any general notification including direct text notifications between users (built in but provided for email alternative delivery) | +| Notify health check | Automatic daily (or any time server is restarted) "ping" notification to confirm notification and Generator system is active at server | +| Object age | Any object of selected Tags and selected Type's Age ("Duration" selected) after creation | +| Object created | Creation of core business object of selected type and tags | +| Object deleted | Deletion of core business object of selected type and tags | +| Object modified | Any changes and saving of core business object of selected type and tags | +| Outside service overdue | Unit sent for 3rd party service is not returned yet and eta date is within selected "Notify before event" | +| Outside service received | Unit sent for 3rd party service has been received back | +| Preventive Maintenance insufficient inventory | Upcoming P.M. order will not have enough inventory (by selected "Notify before event" date) to generate without making a part request | +| Preventive Maintenance stop date | P.M.'s "Stop generating" date is within selected "Notify before event" setting | +| Preventive Maintenance generation failure | Error automatically generating a work order from a P.M. order | +| Quote status age | A Quote has been sitting at the selected status for longer than the "Duration" selected | +| Quote status change | Any _change_ of Quote Status including from no status (new) to a _specific_ selected status ID value | +| Reminder imminent | A Reminder date is within selected "Notify before event" | +| Requested Part received | Part requested via a Workorder has been received | +| Review imminent | A Review date is within selected "Notify before event" | +| Scheduled on work order | Subcriber is the User selected on a newly created work order item scheduled User record | +| Server operations problem | Any timely and serious issue related to internal AyaNova Server operations requiring attention | +| Unit meter reading multiple exceeded | A meter reading entry 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) | +| Unit warranty expiry | A Unit's warranty expiration date is within selected "Notify before event" | +| Work order completed | Service work order is set to any status that is flagged as a "Completed" type of status. (Customer / HeadOffice or staff User notification) | +| Work order not completed on time | Workorder not set to a "Completed" type Status before the work order's _Complete by_ date | +| Work order scheduled service imminent | Subscriber is the User selected on a work order item scheduled User record AND the scheduled date is within selected "Notify before event" | +| Workorder status age | A Workorder has been sitting at the selected status for longer than the "Duration" selected | +| Work order created for customer | Customer notification sent when a service type work order is created for them (or if HeadOffice Contact user, one of their Customers) | +| Work order status set | Workorder Status set to selected Status value | +| Work order total exceeds threshold | The grand total charges of a Work order set to any completed type work order status have exceeded the selected threshold amount (the "Andy") | diff --git a/server/AyaNova/resource/de.json b/server/AyaNova/resource/de.json index af686f79..e1314b59 100644 --- a/server/AyaNova/resource/de.json +++ b/server/AyaNova/resource/de.json @@ -640,7 +640,7 @@ "NotifyEventWorkorderCompletedStatusOverdue": "Arbeitsauftrag nicht rechtzeitig fertig", "NotifyEventWorkorderCreatedForCustomer": "Arbeitsauftrag für Kunden erstellt", "NotifyEventWorkorderStatusAge": "Arbeitsauftragsstatus für die Zeitspanne unverändert", - "NotifyEventWorkorderStatusChange": "Arbeitsauftrag Status geändert", + "NotifyEventWorkorderStatusChange": "Arbeitsauftragsstatus gesetzt", "NotifyEventWorkorderTotalExceedsThreshold": "Der Gesamtbetrag des Arbeitsauftrags überschreitet den Schwellenwert", "NotifyFromAddress": "SMTP-Benachrichtigungsadresse", "NotifyMailSecurityNone": "Keiner", diff --git a/server/AyaNova/resource/en.json b/server/AyaNova/resource/en.json index e1138e27..4b24e513 100644 --- a/server/AyaNova/resource/en.json +++ b/server/AyaNova/resource/en.json @@ -640,7 +640,7 @@ "NotifyEventWorkorderCompletedStatusOverdue": "Work order not completed on time", "NotifyEventWorkorderCreatedForCustomer": "Work order created for Customer", "NotifyEventWorkorderStatusAge": "Work order status age", - "NotifyEventWorkorderStatusChange": "Work order status changed", + "NotifyEventWorkorderStatusChange": "Work order status set", "NotifyEventWorkorderTotalExceedsThreshold": "Work order total exceeds threshold", "NotifyFromAddress": "SMTP notify from address", "NotifyMailSecurityNone": "None", diff --git a/server/AyaNova/resource/es.json b/server/AyaNova/resource/es.json index 6f80ebd3..ef3fb420 100644 --- a/server/AyaNova/resource/es.json +++ b/server/AyaNova/resource/es.json @@ -640,7 +640,7 @@ "NotifyEventWorkorderCompletedStatusOverdue": "Orden de trabajo no completada a tiempo", "NotifyEventWorkorderCreatedForCustomer": "Orden de trabajo creada para la Cliente", "NotifyEventWorkorderStatusAge": "Estado de la orden de trabajo sin cambios durante el período de tiempo", - "NotifyEventWorkorderStatusChange": "El estado de la orden de trabajo cambió", + "NotifyEventWorkorderStatusChange": "Conjunto de estado de orden de trabajo", "NotifyEventWorkorderTotalExceedsThreshold": "El monto total de la orden de trabajo excede el umbral", "NotifyFromAddress": "Notificación SMTP desde la dirección", "NotifyMailSecurityNone": "Ninguna", diff --git a/server/AyaNova/resource/fr.json b/server/AyaNova/resource/fr.json index d1d86d48..f23b5c81 100644 --- a/server/AyaNova/resource/fr.json +++ b/server/AyaNova/resource/fr.json @@ -640,7 +640,7 @@ "NotifyEventWorkorderCompletedStatusOverdue": "Ordre de travail non terminé à temps", "NotifyEventWorkorderCreatedForCustomer": "Bon de travail créé pour le client", "NotifyEventWorkorderStatusAge": "Statut de l'ordre de travail inchangé pour la période de temps", - "NotifyEventWorkorderStatusChange": "Statut de l'ordre de travail modifié", + "NotifyEventWorkorderStatusChange": "État de l'ordre de travail défini", "NotifyEventWorkorderTotalExceedsThreshold": "Le montant total de l'ordre de travail dépasse le seuil", "NotifyFromAddress": "Notification SMTP envoyée depuis l'adresse", "NotifyMailSecurityNone": "Aucun",