ayanova/devdocs/todo.txt

@@ -128,6 +128,14 @@ todo: remove widget now? Back and front (comment out obvs not remove entirely)
 
 ## SERVER MISC ITEMS
 
+todo: Reports need to generate under a file name that is informative (this applies to every object)
+	This is because it will be a common case to need to email them to customers or other users or whatever and it is very helpful to know what it is by name alone.
+	i.e. a workorder should generate a report that can be saved as "Workorder_1" or whatever, 
+	perhaps uses localized name of object but then processed to strip out spaces and case etc (file-name-ify it)
+	Also it will separately need a random part at the end to ensure it's not a dupe of an existing report also generated at the same time
+	Although, if you think of it, doing the same workorder again *should* just overwrite the existing one as it will be identical or at least more up to date so
+	perhaps no need for a nonce
+
 todo: update to latest postgres portable and document how to do it as well or a link to how to do it
 
 todo: errors are inconsistent some use "error" some use "code" to mean the same thing
@@ -192,6 +200,10 @@ What up with this and can it be blocked from logging / something simpler logged
 
 todo: is there a way to tell if other connections are being used to AyaNova db
 	like a utility or they are fucking around and it's affecting performance etc
+	Yes: The following query returns the active connections:https://www.postgresqltutorial.com/postgresql-copy-database/
+		SELECT pid, usename, client_addr 
+		FROM pg_stat_activity 
+		WHERE datname ='dvdrental';
 
 LATER
 ......
@@ -260,26 +272,38 @@ todo: many biz objects are not using new PUT methodology
 
 CURRENTLY DOING: 
 
+	Model affecting cases:
+		https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3866
+			separate status for woitem
+		https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3533
+			outside service decision, keep with unit or separate??
+		https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/2052
+			add engineer signature fields / UI		
+		https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/1908
+			Duration to completed		
 
 OVERALL	
-	- fixup status control 
-		status control should require click to open dialog which shows list of all status prior and allows to add then close to view
-		this way it's clear how to change, less confusing than now and easy to get at the list
-	- woitemtask UI question
-		is this really a collection like scheduled users or labors now??
-		Does it show on a main table in it's own form??n
 
 	- once past this step then second pass at new features **that affect models** (not necessarily UI stuff just fields required etc)
 		Add items below that are just spurious and not tied to a particular case as v.next cases YAGNI/TTM!	
 	- then full in front end and flow out to back end as required, remove any backend that was a defunct evolutionary path so no cruft left around
 	- Keep working on front and back responds to front needs as I go
 	- load and stress test on client
+		This one really needs a e2e test that works and will hammer it so we can run that from multiple locations
 	- ## Try to find every thing that will matter when more collections are added now, ensure a full flow from start to stop and everything in between to try to catch any gotchas now before get too deep into it ##
 
 
-
+todo: cypress testing for load testing etc
+	Look at moving to a standalone Cypress setup, why bother with the one built into vue ui, it doesn't seem to offer any benefits to doing it alone
+	this way can be fully up to date etc
+	https://www.cypress.io/
+	Remove from vue ui project but make copy of tests first
+	then make new project folder for this and put the tests there
+	install standalone cypress and go it without vue stuff
+	
+todo: when fetchign a workorder it should order by woitem.sequence so that reports and things automatically get it in sequence
+	I think in ui it orders automatically at the ui itself in sequence but would need that for reports as well.
 	
-
 todo: changing scheduser estimated qty doesn't trigger dirty until move off, is it using the wrong event for update?
 	gz-decimal control