From d31750be19cd1fc2555600d9ba4327ed9d916a06 Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Wed, 30 Jun 2021 19:18:50 +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 4b931242..437a9693 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -65,9 +65,7 @@ todo: workorders - need to set billing and service address from customers on mig bugbug: direct notification errors out user->direct notification -todo: Customer login should show notifications in app screen always just like regular users in the event that a direct notification is sent - i.e. right now it assumes only needs to show it if they have subscription ability but in-app should always show for direct or error or what have you. - + todo: notifications screen add delete all menu item that will just remove all the notifications present Maybe a checkbox and delete selected and select all?? That way can also be a dual useful feature also should delete *from* the client so that it deletes only what it has in view so user doesn't accidentally delete unseen yet to be delivered ones? @@ -422,8 +420,6 @@ todo: many biz objects are not using new PUT methodology CURRENTLY DOING: -todo: User duplicate locally, improvements, port to customer user form identically - todo: purchase order dupe code at server is a bit sus. it has a todo to set qty to zero but doesn't for some reason so it effectively is affecting inventory on duplicate?? @@ -1301,6 +1297,8 @@ Build 111 - User / Custom contact on create / duplicate now allows entry of new user options before first User save rather than previous behaviour of having to save new record first then edit and save user options +- Customer user login now always shows in App notifications (Bell icon and list when clicked on) regardless of whether they can subscribe to any notifications (global settings) to allow for viewing direct notifications sent to them + - Prevent double booking a tech case 3720 customer request global setting "Allow schedule conflicts" and if on will check if same tech is booked already within that time frame on update or new scheduled user record will not check pre-existing or ones where a match can't be made due to null tech, start or stop date