Forms Best Practices

Naming Conventions

Description

  • A description of what and where the form is used can be extremely useful for audit purposes and peer review tracking.

Fields

  • Name and lookups are set to Autofill horizontally to give more visibility.
  • Other fields default to Compact but may be changed to Autofill if required.
  • Choice fields should be alphabetically sorted unless they are sorted by a categorisation (i.e. priority, severity, critical etc.)

Field Groups

  • Consider using field groups to categorise fields and relationships .

Form Container

  • Typically, the first left hand container will be titled <Object Name> Details.

Form Layouts

  • Forms with multiple Reports can be slow to open. Place Reports in Tabbed Containers to reduce the overall loading time of the Form. By default the first Tab of a Tabbed Container will be 'active' (the 'default Tab') and its content will load immediately.  Content (including Reports) placed in other Tabs only loads when the Tab is activated. 
  • Mandatory fields should be placed directly on the Form, in non-tabbed containers, or in the 'primary Tab' of a tabbed container.  In other words, mandatory fields should be visible without having to search through Tabs. In situations where a field in a 'non-primary tab' must be mandatory there are 2 approaches to consider:
    • Custom Form Validation
    • Conditional Mandatory

Relationships

  • Consider which relationships you want to show. There is an option: "Do not show in reverse".  This does exactly what the name suggests
    • For example: Last Approved By may have little value in the other direction and would just clutter the report and form builder. 

Application Linking

  • It is important that you link your form to your application as this is the main requirement for you to properly package and publish your application later on.