From 11a04314bc0e2b496a840a4ca47dfaef598e6fec Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Thu, 17 Dec 2020 19:50:07 +0000 Subject: [PATCH] --- ayanova/devdocs/todo.txt | 14 +++----------- 1 file changed, 3 insertions(+), 11 deletions(-) diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt index 846e5af6..6996a5f4 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -38,7 +38,7 @@ todo: biz rule like validatecansave and validatecandelete but validatecanFetch f todo: actual customer reports so can figure out datalist for bringing other names in I'm thinking an alternate mode for reporting where there are more defined links in the list to fetch names? - +todo: double check - inactive user should not be involved in notifications at all, it should screen them out automatically and not create or deliver to them TODO: //MIGRATE_OUTSTANDING comment tag search for this comment tag as it will contain items that could not be done until other items were migrated first The tag will contain the description for each @@ -48,18 +48,10 @@ TODO: //MIGRATE_OUTSTANDING comment tag currently doing: Reminder - was regular non followup schedulemarker, Review - was follow up schedule marker - continue case 3511 and reading spec doc to ensure got the gist of it there - - One fleshed out the case do the same for 3425 for Reminders and look into spec docs just in case - - - - -Need to code for both at back end, pay attention to changes in field names in cases +Going to need a bunch of translation keys for both objects Front end may be a bit more time consuming on this one so do the v8 migrate maybe first so have realistic data to work with -v8 migrate schedulemarkers that are followup go to Review -v8 Migrate schedulemarkers that are not follow up go to Reminder + EACH OBJECT DEV CYCLE: