.vscode/launch.json

@@ -53,7 +53,7 @@
         "AYANOVA_FOLDER_USER_FILES": "c:\\temp\\RavenTestData\\userfiles",
         "AYANOVA_FOLDER_BACKUP_FILES": "c:\\temp\\RavenTestData\\backupfiles",
         "AYANOVA_FOLDER_TEMPORARY_SERVER_FILES": "c:\\temp\\RavenTestData\\tempfiles",
-        "AYANOVA_SERVER_TEST_MODE": "true",
+        "AYANOVA_SERVER_TEST_MODE": "false",
         "AYANOVA_SERVER_TEST_MODE_SEEDLEVEL": "small",
         "AYANOVA_SERVER_TEST_MODE_TZ_OFFSET": "-7",
         "AYANOVA_BACKUP_PG_DUMP_PATH": "C:\\data\\code\\postgres_13\\bin\\"

docs/8.0/ayanova/docs/svc-workorders.md

@@ -39,6 +39,8 @@ docs / sections required
     * Part assembly
     * Part request (how they are made and when)
     * Double booking prevention feature in global settings and how it works when scheduling users
+    * "Age" - age is displayed in the workorders data tables as an optional column and is calculated at the moment it's displayed based on the date and time the work order was first created.  
+    * "Time to completion" is displayed in the work order data tables as an optional column and is set whenever a work order is set to a "Completed" status by subtracting the date and time the work order was initially created from the current date and time when the Completed status is saved. If a work order has a time to completion set but is changed to a status that is not a Completed type then it's time to completion is reset to empty.  If a work order has an empty time to completion set and is changed to a status that *is* a Completed type then it's time to completion is set.
 
 ## Work order Cost field visibility restrictions 
 
@@ -123,3 +125,5 @@ As some Work order data is not shown or available to restricted Users, several f
         * UserCanViewLaborOrTravelRateCosts
         * UserCanViewLoanerCosts
 	
+
+