devdocs/todo.txt

@@ -1,9 +1,36 @@
 # now
 
+
+todo: BIG PICTURE
+	prep a release candidate and announce it as such to buy time
+		look for final ayanova 8 changes before doing so in todo's below (high priority stuff only)
+	
+	
+	QBI order of release decision (does raven qbi need to be released along with v8 simultaneously??)
+		if yes then need to whip that shit up pronto with a beta to go with RC for raven
+		figure out how many active qbi users, like will this prevent most people from upgrading?
+		Make a QBI test app but not completely filled in yet in vstudio on v7 laptop then try to open and build in .net core??
+		or figure out the state of .net windows apps, actually also was going to look into platform support for qb desktop api just to see whats out there
+		Beta release QBI (not sure how the fuck that will work or even how to test it but whatever)
+		need a trial of qb desktop maybe
+	
+	Outlook integration extension??
+		wtf to do with that, are there any other extensions actively being sold that I need to worry about?
+
+	Pricing policy and plan
+	New website at the ready
+		including live eval as planned below
+	New Rockfish ASAP
+		should use postgres, need to build site and importer script / code separately
+
+todo: validate the rate limiting by tailing the error log and hitting test raven with a browser and just giong through it all with full refresh to see if it kicks in during standard like rockfish
+
+
 todo: QBOI deprecation
 	done: QBOI removed from website except still in docs and in trial installer
 	done: Product is set to inactive with ShareIt, no one can buy it now
 	OUTSTANDING: I will need to remove it from the AyaNova installer completely 	
+		or maybe not since we will be hiding the v7 download when new website goes up anyway so... :shrug:
 	OUTSTANDING: 
 		There is one single active QBOI user "PITI" Pro-tech IT.ca and they just renewed QBOI so The earlier the better to notify him if it's officially discontinued
 		His QBOI expires 2023-04-18
@@ -28,6 +55,7 @@ todo: licensing and pricing
 			Or do we say v7 is dead as of xx date, v8 will be the new thing and we will give a deep discount to purchase and be on v8??
 
 todo: sunset v7 upon the moment of v8 release
+	email protech it and explain qboi situation
 	move the site to legacy subfolder (search and replace links that point to root url to subfolder url)
 	inform all v7 users that we will be moving v7 to legacy support mode, 
 		offer them a link to test convert to v8 (manual link to v7 migration pages)
@@ -83,23 +111,11 @@ todo: LIVE EVAL NOTES
 
 
 
-TODO: Unit model select template doesn't offer UPC as a field nor does it in Unit though Unit's I guess maybe don't work that way, see v7 to confirm where UPC code was exposed
-	looks like this was forgotten 
-	when enabled go back into unit model docs and UPC field and expand
 
-todo: unit model discontinued date should be hidden until disconitnued is checked in client UI
-
-todo: something in v8migrate level 1 change regarding loan units or something?? 
-	I think it's the only outstanding current issue other than plugins before release and the bits here in this "now" todo section
 
 
 ADD TO DOCS:
-	test server license expired so goes to license request page even though there is data in it and when I enter the license request company name etc it says all data will be erased!?
+
-		must be something to do with expired license but no idea why it would say that fuckery!
-	It's deliberately coded this way in the client UI: if there is existing data and it's an expired *trial* then it will automatically prompt to erase db before it will even send the request
-	this is good, but confusing, maybe a better message indicating what's up? 
-	 Also docs need addition about this issue and process.
-	 not a highly important thing, but should be noted in docs at least
 
 
 TEST IMPORT FILE OPEN ON iPad device as the file input accept type may not work with apple
@@ -140,7 +156,7 @@ start in on QBI
 	todo: (only if winforms is the route to go and .net core supports qb api) figure out how can design forms in vscode for a winform interface, possible build them on v7 laptop, commit and open in vscode just the form design part
 		does .net core support winforms?  Has the form design code format changed from .net?
 
-QBOI?  Fuck QBOI?
+QBOI?  Fuck QBOI, all my homies hate qboi
 	How many actual? one PITI
 	Put last?
 	Focus on qbi
@@ -154,6 +170,14 @@ rockfish front end improvements, revocation, license link that does nothing??
 	product codes or feature options to include??
 	what exactly is rental in the license doing?
 	is license versioned for format?
+	make it a razor pages / bootstrap application
+	better secrets handling rather than in app code or does this matter if server is compromised??
+	use cron jobs to handle licensing notifications etc rather than doing it manually 
+		see https://blog.healthchecks.io/2022/02/healthchecks-io-hosting-setup-2022-edition/ for inspiration
+		cron job can call a .net core app that logs into db and does the work mailing out etc
+
+
+
 
 
 	
@@ -201,7 +225,7 @@ critical path items:
 
 - Plugin / addon replacements implemented and fully tested
 	qbi - 4alarm can't migrate until this is done
-	qboi
+	qboi - no
 	(if pt, well after release if ever)	
 	??? others??
 
@@ -337,7 +361,14 @@ todo: 3 WINDOWS SINGLE LAUNCHER:
 ╚═════╝  ╚═════╝  ╚═════╝ ╚═════╝ ╚═╝     ╚═╝╚══════╝╚═╝  ╚═══╝   ╚═╝   ╚═╝  ╚═╝   ╚═╝   ╚═╝ ╚═════╝ ╚═╝  ╚═══╝
 
 
+todo: 1 10gb is way too high for the file limit in nginx etc, it should be reduced considerably as it allows an attack vector that ties up server
 
+todo: 1 test server license expired so goes to license request page even though there is data in it and when I enter the license request company name etc it says all data will be erased!?
+		must be something to do with expired license but no idea why it would say that fuckery!
+	It's deliberately coded this way in the client UI: if there is existing data and it's an expired *trial* then it will automatically prompt to erase db before it will even send the request
+	this is good, but confusing, maybe a better message indicating what's up? 
+	 Also docs need addition about this issue and process.
+	 not a highly important thing, but should be noted in docs at least
 
 
 ## MIGRATION ITEMS
@@ -351,6 +382,9 @@ todo: 3 WINDOWS SINGLE LAUNCHER:
 	needs to re-work the loaner list and match up the id's of any active work order they are on somehow and then flag that in v8 so 
 	immediately after workorders are exported that's the step to re-run through the loaners and flag them
 
+todo: 1 something in v8migrate level 1 change regarding loan units or something?? 
+	I think it's the only outstanding current issue other than plugins before release and the bits here in this "now" todo section
+
 
 ## TESTING ITEMS
 ████████╗███████╗███████╗████████╗██╗███╗   ██╗ ██████╗ 
@@ -390,6 +424,12 @@ todo:3 todo: check out this SPA memory leak detector, it *does* have a login abi
                                          
 
 
+TODO: 1 NOTE CLIENT/ SERVER/ DOCS ALL:  Unit model select template doesn't offer UPC as a field nor does it in Unit though Unit's I guess maybe don't work that way, see v7 to confirm where UPC code was exposed
+	looks like this was forgotten 
+	when enabled go back into unit model docs and UPC field and expand
+
+todo: 1 unit model discontinued date should be hidden until disconitnued is checked in client UI
+
 todo: 1 BUGBUG - loaner item has a default rate but it's not being used on work orders when selected
 	probably also quotes and pm's as well.
 	NOTE: v7 didn't have a default rate, not sure why I added it, maybe it's better to remove it?
@@ -397,7 +437,12 @@ todo: 1 BUGBUG - loaner item has a default rate but it's not being used on work
 	so after beta but before release should be dropped, or maybe this is my first schema update besides translation?
 
 
-todo: 1 should a superuser really have a dashboard?
+todo: 3 should a superuser really have a dashboard?
+	it's easier for testing purposes but aside from that I don't think so
+	super user should only be used to manage ayanova and other users, not for actual stuff though it needs memos for export notification etc....hmmm...
+	maybe just say fuck it for now
+	Bumped for later re-examine
+
 todo: 2 adm-import lists a lot of objects that are work order item children etc, I think people mainly want invenotry (which isn't there), customers, ho maybe, whatever is the biggest lists
 	so remove unimportable types, implement most desired import types