From 6d72a592b73fce3317b143dfce42aa0a045802ae Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Fri, 30 Jul 2021 22:54:05 +0000 Subject: [PATCH] --- ayanova/devdocs/todo.txt | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt index 9ad1d05b..0f07286f 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -511,11 +511,7 @@ todo:2 many biz objects are not using new PUT methodology CURRENTLY DOING: - - - - Pore over quote and PM and look for workorder remnants, particularly biz actions and rules - + Test generate threshold and etc Test with insufficient inventory on generation and add code to generate request automatically Add new event log event for generation and log it in standard event log @@ -561,6 +557,8 @@ todo MISC: test dupe from all three for all types and confirm PM repeat interval chooser has units in alpha order so days before minutes etc, sb in incremental natural order maybe can sort by ID instead?? + PM exclude days same problem in alpha order, not id order so not in natural day of week order + sort by ID instead Notification code from workorder/quote/pm *item* grandchildren? Why is this a thing? shouldn't it be removed entirely, it's jsut wasted cpu cycles can a user even subscribe to any of these? Should they? Scheduser schedule conflicts - should this not be processed on PM generation??