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

@@ -51,10 +51,12 @@ UI FEATURE - The ability to customize forms:
       
     - Need a FormCustom controller that supports routes for:
         - Routes for customization form populating and receiving
-            - GET (formkey), gets a FormOptions object that combines the data from FormAvailableFields static class with the current custom values if any from the FormCustom table
+            - GET (formkey), gets a FormOptions object that provides the basis for building the form customization view
+                - Also required at the client is the current form customizations if any which can be gotten from the other route for day to day ops below                
             - POST (formkey), accepts a FormCustom object that contains the users customization choices only
                 - Validation ensures "CORE" fields cannot be customized
-                - Localization changes are handled here even though they aren't part of the actual FormCustom table, so split off and separately the localized text is updated
+                - Localization changes are NOT handled here even though it's the same client end form, that is handled at the CLIENT end after it has updated this part separately through regular localized text routes
+                    - To ensure proper separation of concerns
 
         - Routes for the day to day form display purposes that efficiently fetch the form customization to use on demand and caches at the client
             - (GET formkey, token): Given a formkey and an *optional* concurrency token, returns one of the following:
@@ -63,7 +65,7 @@ UI FEATURE - The ability to customize forms:
                         - Basically whatever is in the FormCustom table record for that formkey
                 - If concurrency token provided and is unchanged then simply returns a code 304 (NOT MODIFIED)
 
-
+        - TESTS for the above!!!
     
 
 EXISTING v7: