devdocs/specs/core-notification.txt

@@ -190,7 +190,7 @@ methods they have two entries here, no other table indicates events to be tracke
 		so for example a CreatedWithTag notification or UpdatedWithTag notification will work on any object with that tag if global or a specific type i.e. customer with that tag
 	Then they can control by tag as well, intags are used to filter and include (or any if no intags), outtags filter out and trump intags
 		These are also used for tag type conditions
-	(aID, userId, ayatype, aEventType, advancenoticetimespan, idvalue, decvalue, aDeliveryMethod, deliveryaddress, attachreportid, intags, outtags, HASH) 
+	(aID, userId, ayatype, aEventType, advancenoticetimespan, agevalue, idvalue, decvalue, aDeliveryMethod, deliveryaddress, attachreportid, intags, outtags, HASH) 
 
 /Notifyevent table - contains all events, created by updating objects or directly in some cases and used by generator for processing as deliveries
 	created (timestamp used to clean out old stuck events), ayatype, objectid, eventtype, appliestouserid (single subscriber event), aEventDate, ASAVEDMESSAGE, HASH?
@@ -253,6 +253,7 @@ WorkorderItemPartRequestCreated case 3652 [GENERAL]
 ContractExpiring - Customer version in addition to User version [CUSTOMER]
 WorkorderTotalExceedsThreshold - Custom notification case 1745 "the andy" [GENERAL]  [CONDITION: DOLLARTOTAL money value]
 WorkOrderStatusAge "deadman" delivery if *SPECIFIC* status not changed to different status before XX time period [GENERAL] https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/1137
+	NOTE: this will need a timespan with a different title
 
 QuoteStatusAge [PERSONAL (prepared by), GENERAL]
 UnitWarranyExpiry case 1361 [GENERAL]