.vscode/launch.json

@@ -49,7 +49,7 @@
         "AYANOVA_USE_URLS": "http://*:7575;",
         //"AYANOVA_PERMANENTLY_ERASE_DATABASE":"true",
         "AYANOVA_SERVER_TEST_MODE": "false",
-        "AYANOVA_REPORT_RENDERING_TIMEOUT":"1",
+        //"AYANOVA_REPORT_RENDERING_TIMEOUT":"1",
         "AYANOVA_SERVER_TEST_MODE_SEEDLEVEL": "large",
         "AYANOVA_BACKUP_PG_DUMP_PATH": "C:\\data\\code\\postgres_14\\bin\\"
       },

docs/8.0/ayanova/docs/acc-tax-codes.md

@@ -1,7 +1,5 @@
 # Tax codes
 
-[UNDER CONSTRUCTION]
-
 The Tax codes [form](ay-start-form-overview.md) is used to create and edit taxes in AyaNova.
 
 Tax codes are used to indicate and calculate charge and cost taxes in several areas of AyaNova including on [Work orders](svc-workorders.md).

docs/8.0/ayanova/docs/ay-biz-admin-intro.md

@@ -1,3 +1,6 @@
 # Customization and business administration introduction
+[UNDER CONSTRUCTION]
 #b4beta
-Overview of customization features (translation, templates (picklist, datalist etc)) and admin (Global) setttings with links to each section
+Overview of customization features (translation, templates (picklist, datalist etc)) and admin (Global) setttings with links to each section
+
+This should be an overview of biz admin tasks with links to each or changed to alternative simplified structure.

docs/8.0/ayanova/docs/ay-start-changes-from-v7.md

@@ -1,7 +1,5 @@
 # Changes from AyaNova version 7
 
-## Overview
-
 Starting with version 8, AyaNova was completely re-written.
 Our goals in this were to make AyaNova easier to use, modernize aging code, take advantage of the latest technologies and move to a modern run on any device approach.
 

docs/8.0/ayanova/docs/ay-start-data-types.md

@@ -1,4 +1,4 @@
-# DATA TYPES
+# Data types
 
 ## DATE / TIME TYPES
 
@@ -16,7 +16,7 @@ When viewing data in AyaNova that is filtered, the browser's current time and ti
 
 ### Currency
 
-Currency values are stored with 38 digit precision and 18 digit scale. This means a total of 38 digits can be stored and of those 38 digits, up to 18 can come after the decimal point. This level of precision and scale is more than adequate for most circulating currencies but is necessary to accomodate potential usage of crypto currencies such as Etherium or Bitcoin.
+Currency values are stored with 38 digit precision and 18 digit scale. This means a total of 38 digits can be stored and of those 38 digits, up to 18 can come after the decimal point. This level of precision and scale is more than adequate for most circulating currencies but is necessary to accomodate potential future support for crypto currencies such as Etherium or Bitcoin.
 
 This applies to any item which is a currency amount or a rate used to calculate a currency amount (except taxes see below)
 
@@ -28,16 +28,16 @@ Decimal numbers used typically for quantities of items are stored internally wit
 
 ### Tax
 
-Taxes are stored and displayed in "face" value and not as fractions. So, for example a 7% sales tax is entered displayed adn stored as 7.0 and not .07.
+Taxes are stored and displayed in "face" value and not as fractions. So, for example a 7% sales tax is entered displayed and stored as 7.0 and not .07.
 Taxes are stored with 8 digits precision and 5 digits scale so a total of 8 digits with up to 5 of those 8 after the decimal point.
 
 ### Geographic coordinates
 
-Latitude and longitude are entered and stored in decimal notation format and internally support 9 digits of precision and 6 digits of scale (9 total digits of which 6 can be after the decimal point)
+Latitude and longitude are entered and stored in decimal notation format and internally support 9 digits of precision and 6 digits of scale (9 total digits of which 6 can be after the decimal point).
 
 ### Object Identities / id values
 
-Records created in AyaNova are automatically assigned a sequential id value (per object type) of a large-range 8 byte integer starting at 1 and extending to a maximum id value of 9223372036854775807
+Records created in AyaNova are automatically assigned a sequential id value (per object type) of a large-range 8 byte integer starting at 1 and extending to a maximum id value of 9223372036854775807.
 
 ## TEXT TYPES
 
@@ -45,10 +45,12 @@ Records created in AyaNova are automatically assigned a sequential id value (per
 
 AyaNova general text fields are unlimited in length and fully support Unicode text (including emojis). These are typically things like Name fields or Note fields. While it's possible to enter an unlimited amount of text in some fields it is best to limit the length for practical reasons in areas like Names of objects due to the limited space to display them in some user interface devices. e.g. it's possible to use a 1000 character name for a Customer but would be impractical in display. Keep names short and store any extra data in custom fields or notes fields.
 
+Note that length of text displayable and enterable may be limited by the browser in use.
+
 ### Tags
 
 Tags are special variation of Text type and are stored internally as an unlimited array of _maximum_ 255 characters each. Spaces are not allowed instead a dash symbol - is substituted for spaces and all tags are lower case by default.
 
 ## Custom fields
 
-Custom fields can represent many types but are all stored in the database as a fragment of JSON formatted data and rules for JSON data are applicable regardless of type.
+Custom fields can represent many types but are all stored in the database as a fragment of JSON formatted data in a text field in each business object and rules for JSON data are applicable regardless of type.

docs/8.0/ayanova/docs/ay-start-edit-forms.md

@@ -1,10 +1,67 @@
 # Edit forms
 
-[Under construction]
-#b4beta
+AyaNova business objects are created and edited in edit forms.  Here we detail the common features of edit forms.  Some forms will not have these features if they don't apply, for example there won't be a "View on map" menu item if there is no address for the object being edited.
+
+### Top Application bar
+
+The top portion of an edit form ("App bar") is the primary source for navigation and commands and consists of a bar at the top:
+
+![narrow edit form appbar image](img/edit-form-appbar-green-narrow.png)
+
+This app bar is green indicating the User has the ability to edit the current record.
+
+![narrow edit form appbar gray image](img/edit-form-appbar-gray-narrow.png)
+
+This app bar is grey indicating the User is not permitted to to edit the current record.  Grey app bars can indicate an object is also in a read-only state rather than the User not having sufficient privileges.  For example when a service work order is temporarily set to a read only status.
+
+#### App bar controls
+
+![edit form appbar parts image](img/edit-form-appbar-parts.png)
+
+##### Nav icon
+
+The nav icon or "hamburger" button slides open the navigation pane to move to different main areas of AyaNova.
+
+##### Object type icon
+
+The object type icon is a visual reminder of what type of object is being edited.  All business objects in AyaNova have their own icon to represent them.
+
+##### Object name
+
+The object name is displayed at the top as a visual reminder of which exact object is being edited and also appears in the web page title so that it can be seen on desktop browsers when AyaNova is minimized such as in the Windows task bar.
+
+##### Notification icon
+
+The notification bell icon is always visible in AyaNova and indicates when there are new [notifications](home-notifications.md) that have arrived and how many.
+
+##### Surfaced menu items
+
+When there is enough width to fit, AyaNova will "surface" commonly used menu icons to save a click.  Generally this is the "Save" button on most forms.
+
+#### Menu icon
+
+Menu's that can be opened are always represented in AyaNova by the three vertical dots icon.  Menus at the top of edit forms contain controls related to the overall object.  Menus inside the edit form contain controls related to a specific sub-section of the edit form.  Look for menu controls to see further actions that can be taken in forms.
+
+### Edit form body and fields
+
+#### Responsive display
+
+AyaNova uses a grid system to automatically lay out the contents of the edit form appropriate to the width of the browser window.  
+
+In narrow view devices such as smart phones and small tablets AyaNova will display a single vertical column of all form fields.  This expands up to 4 columns wide on the widest browser windows on wide screen devices such as a typical PC monitor.
+
+#### Error and alerts
+
+![edit form alert types image](img/edit-form-alert-types.png)
+
+
+
+### Common edit form menu options
 
 #### Save
 
+The Save 
+
 #### Delete
 
 #### Report

server/AyaNova/biz/FormFieldReference.cs

@@ -822,7 +822,7 @@ namespace AyaNova.Biz
                     //WORKORDER 
                     List<FormField> l = new List<FormField>();
 
-                    l.Add(new FormField { TKey = "WorkOrderSummary", FieldKey = "WorkOrderSummary" });
+                    l.Add(new FormField { TKey = "WorkOrderSummary", FieldKey = "Notes" });
                     l.Add(new FormField { TKey = "WorkOrderStatus", FieldKey = "WorkOrderStatus" });
                     l.Add(new FormField { TKey = "Address", FieldKey = "Address" });
                     l.Add(new FormField { TKey = "WorkOrderCloseByDate", FieldKey = "WorkOrderCloseByDate" });
@@ -1686,7 +1686,7 @@ namespace AyaNova.Biz
     public class FormField
     {
         //CLIENT / SERVER Unique identifier used at BOTH client and server
-        //MUST MATCH MODEL PROPERTY NAME EXACTLY
+        //MUST MATCH MODEL PROPERTY NAME EXACTLY OR REQUIRED FIELD VALIDATION WON"T WORK
         public string FieldKey { get; set; }
 
         //CLIENT Use only for display in customization form