There are two types of forms within the system. Content forms comprise a set of questions that are used to capture details about photographs, videos, documents or any other useful set of information. For example, a ‘Photograph' form may be designed to prompt the user to enter a caption for the photograph, the photographers name and the people that are shown in the photo. System forms are basic lists of values that can be stored within the system for use on multiple occasions. For example, the 'Months of the Year' system form contains 12 entries - 'January' through 'December'. These entries can then be efficiently added to any content form that requires this information - for example as a dropdown selection on a 'Calendar' content form.

1. Click on the [Settings] tab and click on the 'Add form' (+) icon. *Note: This will automatically add a content form. To add a new system form, continue to the following step.

   
   

2. Alternatively, click on either the 'New form' or 'New system form' link the header area of the [Form] section.

   

3. You will then be able to configure the new form by setting its Appearance, Permissions, Restrictions, Configurations and Customisations. Many of these settings and fields are optional. See below for more information about a specific setting.

   Appearance

   1. 1. Form label - This is the name used widely to describe the form content (e.g. People, not Person).

      2. Single form label - This should be a term describing one entry of this form. It is used when interacting with one entry (e.g. Add Person). NOTE: If you don't specify this, it is auto-populated based on the form label.

      3. Standard form/table name - This name is used for aligning with data standards and sources. It must be unique within the system and is used to auto-match fields/columns when importing data. NOTE: If you don't specify this, it is auto-populated based on the form label.

      4. Set as system form - If set, this form is treated as a system form. The main impact of this setting is that entries will be excluded from search results.

      5. Layout type - This option determines how entries of this form are presented.

      6. Define form icon - The form icon is used widely throughout the system. It is expected to be black with some transparency so that system layout colours show through it. It is inverted (to white) when displayed over dark backgrounds.

      7. Form colour - Select a colour that will be used to when representing entries of this form on the map. This is recorded at a HTML colour code (e.g. #336699).

      8. Description - If set, this text describes the purpose/scope of this form. You may include information how it is used, how it interacts with other forms, etc.

      9. Choose representative image - If set, this image is shown along with the description text when browsing the form entries.

   Permissions

   1. 1. Default 'view only' group(s) - The group(s) chosen here are pre-filled into the 'Who can view this' section of the 'Sharing rules' for new entries.

      2. Default 'view and edit' group(s) - The group(s) chosen here are pre-filled into the 'Who can view and edit this' section of the 'Sharing rules' for new entries.

   Restrictions

   1. 1. Set form as locked - If set, users are not able to add new entries of this form.

      2. Enforced 'Can Add' group(s) - The group(s) chosen here are the only groups that can 'Add new' entries. If no groups are defined, is is assumed all groups are allowed. NOTE: Users can still view entries of this form if they are shared with them. They just won't be able to add additional entries.

   Configure

   1. 1. Position - If set, the value overrides the default alphabetic sort of forms when presented to users. This is useful for forcing commonly used forms into a pre-defined order.

      2. Fulcrum form identifier - This should be set to the matching GUID when there is a need for alignment with a particular form designed in Fulcrum.

      3. Configuration - Key=Value pairs can be added in here to activate special configuration options for the form.

   Customise

   1. 1. Symbology - If set, this overrides the form colour. This requires following OpenLayers 2 syntax for defining symbology (see reference).

      2. Markup for before form - All markup entered here will be rendered on the entry before the form.

      3. Markup for after form - All markup entered here will be rendered on the entry after the form.
         
         

4. Click [Save] to finalise your changes and create the new form.

   
   

5. For further information about how to customise your new form, see How do I customise a form?