From d834e9a1a02b2187a78753c94f91e71b88cbe374 Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Sun, 26 Sep 2021 17:11:43 +0000 Subject: [PATCH] --- ayanova/devdocs/todo.txt | 32 ++++++++------------------------ 1 file changed, 8 insertions(+), 24 deletions(-) diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt index dedbe340..9ff61dfe 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -7,8 +7,14 @@ "Make it happen" - Jim July 28th 2021 + + ## ROUGH SCHEDULE + + + + todo: release then test sched from linux server just to ensure no unexpected issues. Test with ipad and table and phone as well. # Schedule form @@ -271,7 +277,7 @@ todo: 3 Schedule form reporting? todo: 1 Reviews need to be removed when corebiz are deleted (any reviewable object) see customer delete for example, probably need to move this to a static function in Review since it will be called from everywhere should be a bizobject built int? - +todo: boot complete server open message to console should include server version number todo:1 update to latest postgres portable and document how to do it as well or a link to how to do it todo: 1 if a customer type logs in, does Auth check to see that customer or headoffice is active? because if it isn't the user shouldn't be allowed to login either @@ -772,28 +778,6 @@ MID CENTURY MODERN TUNES - https://www.allmusic.com/album/ultra-lounge-vol-14-bo -BUILD 131 CHANGES OF NOTE +BUILD 132 CHANGES OF NOTE -- case 3946 -- Added work order states collection to report data for work order and status viz fields: Name, color, completed, locked -- Added work order item status and priority Name and Color fields as viz fields to report data for work order -- Review object added ReviewObjectViz field to report data which will have name of reviewed object or if it's not a named object the translated object type name instead -- Added personal schedule form (home-schedule) for initial UI testing before implementing other schedule form based stuff such as service-schedule and others -- case 3955 back to you -- case 3963 -- case 3968 -- case 3969 -- case 3971 -- case 3972 sample code and info provided -- case 3973 fixed and included note about errors that go by too fast -- case 3974 duplicate -- case 3975 standardized -- case 3976 -- case 3977 info provided -- case 3979 -- case 3980 could not reproduce, likely fixed by earlier case -- case 3981 -- case 3982 -- case 3983 -- case 3984