anchor.diff:  and modify the JSON files under the new directory
   ====
   
  +[[customization-enduser-form]]
   ===== Form customization
   
  -User self create/edit form could be customized in order to:
  -
  -* Hide/show some attributes
  -* Deny/allow attribute write
  -
  -Under the `enduser/src/main/resources` directory you can find `customForm.json` file.
  -This specifies the rules about form customization, in particular it allows to customize `PLAIN`, `DERIVED` and `VIRTUAL`
  -attributes forms.
  +The <<enduser-application>> allows to customize the form in order to:
  +
  +* hide / show attributes
  +* set attributes read-only for users
  +* provide default value(s)
  +
  +Under the `enduser/src/main/resources` directory, the `customForm.json` file is available, allowing to configure form
  +customization.
  +
  +[NOTE]
  +.Hot deploy
  +====
  +The `customForm.json` could be edited and reloaded without the need of re-starting the Java EE container.
  +====
   
   [TIP]
  -====
  -The file provided with the archetype contains an empty json: `{}`.
  -If such file is deleted or contains empty or not parseable json, customization will be simply ignored and all attributes
  -will be shown.
  -====
  -
  -Here is an example:
  -
  -```
  +The `customForm.json` default content is just an empty object `{}`: if such file is missing, empty or not valid,
  +form customization will be simply disabled and all attributes will be shown.
  +
  +.Sample form customization
  +====
  +[source,json]
  +----
   {
  -  "PLAIN": 
  +  "PLAIN":
             {
               "show": true,
               "attributes": {
  
positive.code:             }
            }
  }
  ```
  As you can see the file has two main levels:
  
  * Schema type: `PLAIN`, `DERIVED`, `VIRTUAL`.
  * Attributes: list of attributes (by schema type) to be shown in the form.
  
  ====== Schema type
  
  The schema type level allows to define customization of the three sub-forms available in the wizard.
  An user can specify one or each of the three sections in order to customize only what is really needed.
  Though enable/disable of schema forms can be configured also from the `app.js` file of the enduser, form customization
  json provides an attribute `show` to hide/show attributes input fields.
  If `show` is set to `false` info contained into `attributes` will be ignored and nothing is displayed in the form section.
  
  ====== Attributes
  
  Attributes level contains a map of attributes to show.
  
  [TIP]
  ====
  Attributes map is meant to be populated, i.e. empty `attributes` field means "do not filter at all and show all attributes".
  For example:
  ```
  {
    "PLAIN": 
  
negative.code:           {
              "show": false
            },
    "VIRTUAL":
            {
              "show": true,
              "attributes": {
  