Form Personalization

Form Personalization is a feature of OneDealer where the user can personalise the view of the form such as field order and show/hide any non required, by the system, fields.

In addition, if the user has the business case 12098 (form designer business case), the system provides the following validation features:

• Required
• Validation rules with regular expression (only for text fields ,provided also with autocomplete, by the system, suggestions)
• Masking (only for text fields , e.g. License Plate, Phone number)
• Max length validation (only for text fields)

With this business case, the user can save the changes as a default form for all the other users (the user can overwrite the forms served by the system).

Screenshots

Step-by-step guide

1. Go to a page (Pages with form personalisation as example are Business Partner, Vehicle, Contact Person)
2. At the bottom of the page / tab, exists a link with text "Form Personalization", select it to open the form personalization dialog (pop up form).
3. Inside the pop up form are displayed the form fields categorised in section as in the page.
4. The checkbox left to the name of the control is whether we want the control to be displayed or hidden in the page
5. On the right there are the ordering arrow button. By selecting them the control is moving one place after or before.
6. Next to the arrow control and if the user has the business case 12098 , there is the validation settings button, which by clinking on it, it displays down from the control name, the validation settings form, where the user can edit the following:
   1. Required field
   2. Validation rules with regular expression (only for text fields, provided also with autocomplete, by the system, suggestions)
   3. Masking (only for text fields , e.g. License Plate, Phone number)
   4. Max length validation (only for text fields)
7. Select Save to save the changes or Cancel to discard them.
8. If user has the business case 12098 , there is a button with text "Save as default", which saves the changes for all users as a default form design.

[
  {
    "Description": "Only Digits",
    "Pattern": "^[0-9]+$",
    "ResourceKey": "",
    "ErrorMessage": ""
  },
  {
    "Description": "Decimal Numbers",
    "Pattern": "^\\d*\\.\\d+$",
    "ResourceKey": "",
    "ErrorMessage": ""
  },
  {
    "Description": "Alphabetic Characters",
    "Pattern": "^[a-zA-Z]+$",
    "ResourceKey": "",
    "ErrorMessage": ""
  },
  {
    "Description": "Alpha-Numeric Characters",
    "Pattern": "^[a-zA-Z0-9]+$",
    "ResourceKey": "",
    "ErrorMessage": ""
  }
]

Update (  QA-331 - Getting issue details... STATUS ) :

The following logic has been implemented:

When an admin user configures the personalization form the only setting remains active (in user's configuration) is the order.

Also if a field, in admin configuration, is not required and not visible, then the visible setting in user's configuration is set.