ayanova/devdocs/todo.txt

@@ -183,7 +183,7 @@ Coded by importance
 
 
 TODO: 1 DOCS MUST BE VERSIONED
-	put the release version into the index page of docs prominently e.g. "Version 8.0.0-beta.0.7"
+	put the release version into the index page of docs prominently e.g. "Version 8.0.0-beta.0.8"
 	This is because when code changes docs often will change and they must be matched so this is a way to check that
 
 TODO: Hardware requirements should be 2gb minimum due to printing, 1gb would work if not printing a large load
@@ -293,14 +293,6 @@ TESTING INFO:
 
 
 
------
-
-
-- 1 todo: cancellable reporting?? Jobify it just like any other long running job, it's necessary unfortunately and then put a cancel button
-
-	- upload and test on devops
-	- give to Joyce to mangle
-
 - 1 todo: add the caching technique to *all* the other getreportdata methods as was done with workorder 
 
 
@@ -848,39 +840,10 @@ https://www.ayanova.com/download/ayanova-windows-x64-single-setup.exe
 https://www.ayanova.com/download/v8-migrate.exe
 Current v8 docs home: https://www.ayanova.com/docs/
 
-BUILD 8.0.0-beta.0.7 CHANGES OF NOTE
+BUILD 8.0.0-beta.0.8 CHANGES OF NOTE
+
+
 
-- fixed bug in history that would bomb if a taskgroup name needed to be displayed
-- many minor changes to support e2e testing
-- new download urls case 4053 for details
-- new docs folder hosting current version of v8 docs https://www.ayanova.com/docs/
-	this is for our use so don't need to spin up a server to view the docs but will likely be the permanent url for v8 docs once all is done
-	I have coded everything so that users will go to their *own* server's docs page not our server when they want to read docs to save us traffic etc
-	however we will need a static place for docs when we post them on our site for explaining specific situations or when emailing someone a help link and that's what this will be for
-- fixed query bug in workorderlist AGE column incorrectly calculated
-	note that it may or may not be daylight saving time aware, I'm not sure at this point as it depends on a lot of 3rd party stuff between os's and postgre etc
-	but history will be on our side in any case as most places will be getting rid of DST at some point so it won't matter then.
-	It's potentially possible that it's age is out by an hour if there is a DST change between now and when the wo was created
-	Note that this AGE value is not used for anything other than displaying to the user so it's not going to break anything if it is out by an hour in some cases.	
-- Added caching to workorder report viz field resulting in a 160% report rendering speed improvement in a test of 100 workorders
-- Added caching to pm, quote report viz fields (more to come later)
-- fixed "Service Dispatch" report template that had a duplicate translation key in it: "WorkOrderItemPartQuantity"
-	(note you can check for this during report development by looking at the server log which will show the following error when the report is rendered:
-	2021-12-22 16:19:07.0290|ERROR|AyaNova.Biz.TranslationBiz|********* GetSubsetAsync problem: Duplicate keys: WorkOrderItemPartQuantity)
-- Removed AYANOVA_REPORT_RENDERING_SLOTS setting, no longer required
-	now there are infinite slots available, no limit as this was never the issue and the timeout changes below will automatically take care of any
-	report rendering that is in progress for too long and will if necessary kill the chromium process 
-- Changed how AYANOVA_REPORT_RENDERING_TIMEOUT setting is used and interpreted
-	- setting is now in minutes not milliseconds
-	- docs updated to reflect how it works
-	- this setting is now an overall timeout for the entire report rendering process, will stop any processing if it goes over this limit and return an error to the user, see docs for more info
-	- New automatic server job added that checks every 5 minutes for stuck report rendering processes (ones that went over the AYANOVA_REPORT_RENDERING_TIMEOUT setting) and terminates them
-	- changed display message and help link at web app end for when a timeout happens with clear docs on what to do
-	- Default settings for time out are a best guess by me and we should figure this out as we run into it until we have a sane default for most people as the ultimate release value.
-		For now I'm defaulting to 5 minutes timeout for report generation and hard caps of no less than 1 minute and no more than 15 minutes no matter the setting people use
-		Let me know if 5 minutes is not a high enough default or 15 is not max enough as you test it out
-		It should be as low as possible to run all stock reports with reasonable amount of records but no higher as it could easily eat up all available memory if people go crazy with it
-- Added stock report templates from 20211223additionalreporttemplates.zip
 
 
 

ayanova/package-lock.json

@@ -1,6 +1,6 @@
 {
   "name": "ayanova",
-  "version": "8.0.0-beta.0.7",
+  "version": "8.0.0-beta.0.8",
   "lockfileVersion": 1,
   "requires": true,
   "dependencies": {

ayanova/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ayanova",
-  "version": "8.0.0-beta.0.7",
+  "version": "8.0.0-beta.0.8",
   "private": true,
   "scripts": {
     "serve": "vue-cli-service serve",

ayanova/src/api/ayanova-version.js

@@ -1,4 +1,4 @@
 export default {
-  version: "8.0.0-beta.0.7",
+  version: "8.0.0-beta.0.8",
   copyright: "© 1999-2021, Ground Zero Tech-Works Inc."
 };