devdocs/coding-standards.txt

@@ -14,7 +14,7 @@ Error messages / Numbers
 	- Make sure Every error has a number and that is documented in the manual
 	- Locale keys for error numbers??  i.e. E1000, "blah blah error 1000"
 
-Cleanup and sticking to the following code convention:
+C# code convention:
 	All names are PascalCaseOnly with the following two exceptions:
 		- function paramenter names are ALWAYS camelCased
 		- CONST values are  ALL_CAPS with underlines between for spaces

devdocs/specs/core-customize-form-fields.txt

@@ -16,7 +16,7 @@ UI FEATURE - The ability to customize forms:
         - If a dispatcher needs a custom field set on a workorder, a bizadminfull user must login and set that up for them
         - When customize is selected a generic form pops up with a list of fields provided by the backend and their current settings and controls
             - This form can then be re-used everywhere as it's a stock object and this way we don't need to have a customize form for every existing CRUD form
-    - Choosing to expose one or more of up to 15 custom fields on form in custom field section that shows when at least one is enabled
+    - Choosing to expose one or more of up to 16 custom fields on form in custom field section that shows when at least one is enabled
     - Set the localized text for the current locale for every existing field and any custom ones enabled
     - Set whether a field is visible or not to user
         - Some stock fields will never be able to be hidden, they will be "core" fields required for AyaNova operations and will have their hidden checkbox grayed out
@@ -27,7 +27,8 @@ UI FEATURE - The ability to customize forms:
     - Client caches the customization data when it first opens the form and then checks if it's changed when it next opens the form
         - The route that fetches the FormCustom data needs to accept a query item that is a date or concurrency token so that 
         if nothing has changed the server returns the unchanged code or instead returns all the data if it is changed to save bandwidth
-
+    - RAVEN custom fields start with 1 not zero like in v7
+        - Import v7 custom0 to RAVEN custom1
     
    
 ## TODO
@@ -42,7 +43,7 @@ UI FEATURE - The ability to customize forms:
 
     - Need a FormAvailableFields static collection class that contains the fields available to each form
         - This should be independent from any other class tied to a particular route or controller or db table as it could be some or none of all of those things
-        - Method: GetFields(FormKey): FormKey, FieldKey (localekey), Core (bool, true means can't be hidden), IsCustom (bool, means it's one of the custom fields that can be set to type etc)
+        - Method: GetFields(FormKey): FieldKey (localekey), Core (bool, true means can't be hidden), IsCustom (bool, means it's one of the custom fields that can be set to type etc)
         - Method: GetForms() returns a list of form names
         - Method: IsValidForm(string formKey) bool exists or not
         

devdocs/specs/core-import-v7.txt

@@ -89,3 +89,8 @@ NOTES FOR DOCS
     - PartCategory
     - DispatchZone
     - ScheduleableUserGroup
+
+
+- CUSTOM FIELDS
+    - RAVEN custom fields start with 1 not zero like in v7
+    - Import v7 custom0 to RAVEN custom1

devdocs/todo.txt

@@ -14,6 +14,10 @@ Do the stuff in the Client todo first then back to the server as required.
 SERVER
 
 	- PickListFetcher: WTF?  It has a reference to widgetbiz in it, isn't this a generic class??
+
+	- Resource localization edit all Custom field locale keys for all langauges and change to be 1 to 16 (remove 0 and add 6 more)
+		- So, for example ClientCustom0 becomes ClientCustom1 and make sure the display values are identical as right now there are "My Custom0" and "Custom Field 8" in the same bunch
+			- Copy from WidgetCustom1 to 16 if necessary or for reference
 	
     - CUSTOM FIELDS?!
 	- CUSTOM FIELDS (case 3426)