admin/raven-client
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Browse Source
This commit is contained in:
John Cardinal
2021-12-24 17:38:49 +00:00
parent 0c94510911
commit 5fda9193b1
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
ayanova/devdocs/todo.txt
View File

@@ -444,7 +444,7 @@ todo: 1 When there is a rendering issue with chromium browser startup the server
todo: 2 Log levels are all over the place at the server, follow proper guideance and adjust them as per:
https://docs.microsoft.com/en-us/dotnet/api/microsoft.extensions.logging.loglevel?view=dotnet-plat-ext-6.0
specifically there are a lot of log debugs that should be traces and maybe missing log criticals level for server stopping shit
todo: 2 wrap this error in a debug build block before release:
2021-12-22 16:19:07.0290|ERROR|AyaNova.Biz.TranslationBiz|********* GetSubsetAsync problem: Duplicate keys: WorkOrderItemPartQuantity)
@@ -790,8 +790,7 @@ BUILD 8.0.0-beta.0.6 CHANGES OF NOTE
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
- 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)
@@ -807,7 +806,8 @@ BUILD 8.0.0-beta.0.6 CHANGES OF NOTE
- 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