ayanova/devdocs/todo.txt

@@ -302,6 +302,13 @@ console.log(parseFloat(localeParseFloat("1,100.9", "nl"))); // Dutch locale: rev
 
 
 
+- 1 todo: what the fuck is the suggested part quantity, it's not referenced anhywhere but in the docs and doesn't seem to have been coded in the v8 migrate
+	to ghrough the history of commits and see if there is a time it was removed due to some other changer or is it just not implemented properly as documente din ay-biz=admin-migrate
+	#### Work order item parts not "Used in service"
+
+v8 work order item part affects inventory immediately when entered and saved but in v7 inventory is not affected until "Used in service" is checkmarked. For this reason, v7 work orders with work order item parts **not** checkmarked Used in service will have those quantities migrated to the "Suggested quantity" field instead of the Quantity field. This is to ensure that inventory remains in balance after migration.
+
+In v8 Users will need to either use the "Realize suggested part quantities" command in the work order to automatically copy the suggested amounts to the Quantity field in all work order item part records for that work order or manually enter each one in the quantity field as appropriate.
 
 
 -1 todo: why should user be able to open a part inventory transaction record in the first place?  It opens to the history form, isn't that weird, theres nothing to see that isn't 
@@ -310,6 +317,8 @@ in the grid is there??
 - 1 work order item parts and subcontractor restricted has option "REalize suggested part quantities" this should not be available and not for any restricted user	
 	as they are not allwoed to edit parts normally
 
+- 1 work order items context menu, if there are no suggested parts, hide the "realize suggested part quantities" or move it elsewhere, it's annoying and only related to migration I think
+
 - 2 todo: when hide a section in wo like all tasks in customize should hide the add task woitem context menu item too
 - 2: the home notify subscription table shows object types but without the square brackets around them and should for consistency
 - 2: address "Required" uses street as the only required, however it should also alternatively accept latitude longitude instead of a street address for required validation