ayanova/devdocs/todo.txt

@@ -383,17 +383,12 @@ todo: many biz objects are not using new PUT methodology
 
 
 
-CURRENTLY DOING: Work order notifications - PartRequested
+CURRENTLY DOING: Work order notifications - weird new object below then finish off rest of notifications
+
 
-todo: add unit required rule to backend woitemunits selection
-todo: search workorder tree for front end required and other rules then replicate at back end, some are missing and moer will be missing after below blocks of new wo issues fixed
 todo: wokrorderitemloand and possible others have weird NEW object with items from other objects due to copy and paste, clean that shit up, don't need to send it over the wire every time 
 	Go through each and make sure there are exactly the same keys of a fetched record in there (minus viz of course)
 
-bugbug: new wokrorder adding new item of any kind doesn't trigger dirty
-
-bugubg: completely fresh workorder riddled with errors when attempting to create one of each type of record
-
 
 Steps to test notifications:
 	plain in app delivery

ayanova/src/components/work-order-item-outside-services.vue

@@ -662,7 +662,7 @@ export default {
       this.value.items[this.activeWoItemIndex].outsideServices.push({
         id: 0,
         concurrency: 0,
-        unitId: 0,
+        unitId: 0, //zero to break rule on new
         notes: null,
         vendorSentToId: null,
         vendorSentViaId: null,
@@ -683,6 +683,15 @@ export default {
       this.$emit("change");
       this.selectedRow = [{ index: newIndex }];
       this.activeItemIndex = newIndex;
+      //trigger rule breaking / validation
+      this.$nextTick(() => {
+        this.value.items[this.activeWoItemIndex].outsideServices[
+          this.activeItemIndex
+        ].unitId = null;
+        this.fieldValueChanged(
+          `Items[${this.activeWoItemIndex}].outsideServices[${this.activeItemIndex}].unitId`
+        );
+      });
     },
     unDeleteItem() {
       this.value.items[this.activeWoItemIndex].outsideServices[