devdocs/specs/core-notification.txt

@@ -42,6 +42,12 @@ OBJECTS Saving an object triggers notification processing for that object:
 			FUTURE may have alternatives here
 			DUPES are ignored 
 		This table is consulted for all decisions about notifications, no more eventofinterest separate table nor subscriber
+		DUPES - there can be near dupes here because user may have multiple of identical but vary in only:
+			Delivery method
+			advancenoticetimespan (e.g. contract expiring could be one 90 days in advance to renegotiate and then one 10 days in advance for notify service to cancel etc)
+
+		CONDITION
+			has optional condition fields (in v7 was guidvalue for wo status type, but we need more [investigate?])
 	- DELIVERY METHODS
 		no more date ranges for delivery windows
 		Two methods initially
@@ -89,7 +95,7 @@ ALL EVENT TYPES INITIAL RELEASE
 
 
 ## OLD
-WorkOrderStatusChange [GENERAL]
+WorkOrderStatusChange [GENERAL] [CONDITION: STATUS]
 ContractExpiring (User notify, add more notify before time frames in cases) [GENERAL]
 CSRAccepted [CUSTOMER]
 CSRRejected [CUSTOMER]