devdocs/specs/core-custom-fields.txt

@@ -1,9 +0,0 @@
-# Custom fields specifications
-
-## TODO
-
-- https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3426
-- https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/1442 
-
-REQUIREMENTS / CHANGES
-

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

@@ -0,0 +1,53 @@
+# Customize form fields specifications
+
+
+CASES
+    - https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3426
+    - https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/1442 
+    - https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/1368
+    - https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3408
+
+
+
+REQUIREMENTS
+
+FEATURE - The ability to customize forms:
+    - A "Customize" option in the Action bar menu | that is accessible to people of BizAdminFull role only
+        - 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
+    - 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
+    - Set whether a field custom or stock is required to have a value entered or have it's value changed
+        - If required then it's like a business rule and treated just like that at the back and front end
+        - During business rule validation check at backend it checks if the fields are required and have entries and returns a validation error if not exactly the same as for built in rules        
+    - Ideally this would be a better feature if it was everywhere, not just in a limited set of objects but rather in all substantial objects
+    
+
+
+
+
+
+## TODO
+
+EXISTING v7:
+- 10 custom fields in   
+    - Client
+    - Contract
+    - HeadOffice
+    - LoanItem
+    - Part
+    - Project
+    - PurchaseOrder
+    - Unit
+    - UnitModel
+    - User
+    - Vendor
+    - WorkorderItem
+
+
+RAVEN REQUIREMENTS / CHANGES
+
+

devdocs/specs/core-roles.txt

@@ -39,6 +39,8 @@ Basically the v7 manager account stuff with full rights to everything other than
 - Grants roles to other users
 - Licensing
 - Business related configuration settings
+    - Form customization
+    - Localized text customization
 - All management and KPI stuff
 
 ### DispatchLimited
@@ -52,10 +54,13 @@ Basically the v7 manager account stuff with full rights to everything other than
 ### Accounting
 
 ### TechLimited
+Can make entries into existing workorders, add rows to existing areas in the workorder but can't add a new area or create a new workorder
 
 ### TechFull
 
 ### SubContractorLimited
+Like a tech limited but more limited in some ways to be determined (mostly not seeing any private data).
+Can make entries into existing workorders, add rows to existing areas in the workorder but can't add a new area or create a new workorder
 
 ### SubContractorFull
 
@@ -66,7 +71,8 @@ Basically the v7 manager account stuff with full rights to everything other than
 ### OpsAdminLimited
 
 ### OpsAdminFull
-backup, troubleshoot, dashboard of throughput, db administration, all the stuff needed to keep RAVEN up and running and monitor any issues in operations of it, nothing to do with business stuff or actual business data
+backup, troubleshoot, dashboard of throughput, db administration, all the stuff needed to keep RAVEN up and running and monitor any issues in operations of it, 
+nothing to do with business stuff or actual business data