ayanova/devdocs/todo.txt

@@ -383,34 +383,13 @@ todo: many biz objects are not using new PUT methodology
 
 
 
-CURRENTLY DOING: Work order notifications
-
-
-
-Steps to test notifications:
-	plain in app delivery
-	email delivery
-	non matching tag doesn't trigger delivery
-	matching tag triggers in app / email delivery
-
-Coded, tested, done:
-	WorkorderCompletedStatusOverdue
-	WorkorderStatusChange
-	WorkorderStatusAge
-	ScheduledOnWorkorder
-	ScheduledOnWorkorderImminent
-	OutsideServiceReceived
-	OutsideServiceOverdue
-	CustomerServiceImminent
-	WorkorderTotalExceedsThreshold
-	WorkorderCompleted
+CURRENTLY DOING: 
 
 
 todo 3: workorder notifications to code and test:	
 	
 	
-	WorkorderCreatedForCustomer = 31, //*Service work order is created for Customer, only applies to that customer user notify sub for that customer, customer id is in conditional ID value for subscription
-	This is a v7 feature and needs to be replicated
+	 todo test this
 
 
 
@@ -1288,21 +1267,24 @@ build 110
 - Workorder inventory implemented
 	including part requests trigger and system in workorder and backend
 
-- workorder based notifications implemented
+- workorder based notifications implemented	
 	WorkorderCompletedStatusOverdue
-	CustomerServiceImminent (customer user feature)
 	WorkorderStatusChange
 	WorkorderStatusAge
-	OutsideServiceOverdue
-	OutsideServiceReceived
 	ScheduledOnWorkorder
 	ScheduledOnWorkorderImminent
-	WorkorderCompletedStatusOverdue
+	OutsideServiceReceived
+	OutsideServiceOverdue
+	CustomerServiceImminent
+	WorkorderTotalExceedsThreshold
+	WorkorderCompleted (customer and inside user notification, properly works with headoffice type users and their customers)
+	WorkorderCreatedForCustomer (customer notification, properly works with headoffice type users and their customers)
 
 - standard object CRUD notifications implemented for all workorder tree objects
 	(note that child items in workorder tree that don't have their own tags [all but items and workorder item units] will use the work order header tags for determining notification)
 
 - Administration -> Global settings form added all Customer "contact" login account related control settings
+	also implemented at UI so those settings will now affect what Customer or HeadOffice user sees when they login or attempt to subscribe to a notification
 	
 - Removed all visible references to Service Bank feature from all forms and front and back end
 

ayanova/src/views/home-notify-subscription.vue

@@ -780,7 +780,7 @@ async function populateSelectionLists(vm) {
           return window.$gz.store.state.customerRights.notifyCSRRejected;
         case 21:
           return window.$gz.store.state.customerRights.notifyServiceImminent;
-        case 30:
+        case 30: //cust or inside user both
           return window.$gz.store.state.customerRights.notifyWOCompleted;
         case 31:
           return window.$gz.store.state.customerRights.notifyWOCreated;