# General Concepts A form is the backbone of every Daxium-Air application. It defines the structure of the data you collect — the list of fields, their types, and their display rules. You may also hear it referred to as a **module** or a **checklist** depending on the context. Administrators are the ones who design and configure forms; field users only interact with the submissions created from them. A form allows you to collect information whose type is defined beforehand. ## Creation To access the form creation page, you must first click on the icon below: ![](/files/idt2nxFIcKjjVfVO8NaY) This gives you access to various settings menus, including the "Data and Forms" and the "Forms" sub-menu, present on the left as well as in the center of the page: ![](/files/DAP6DJVF5kP61XjYZgb5) After clicking on "Forms", you can click on "New" : ![](/files/K8sAoT2fTrDH3RduQWoH) The first step is to name the form at the top right. A form is made up of fields of different types. You can drag the desired field into the frame in the position you want or press the little “+” when you hover over the field with the mouse, it will then be added after the others. ![](/files/3lkL18PxI0h8bh264v3Y) The **”system name”** of the fields is what identifies the field in the system, it must be unique within a form and related forms. It is used in [reports](/user-documentation/build/building-the-reporting/syntax-functions.md), [conditions](/user-documentation/build/building-forms/conditions.md) and adjustable parameters depending on the content of the fields (emailing for example). The **”wording”** is what the user sees. user, on the web or on mobile. ![](/files/Ez62ghUjVrZj0aiPJO4B) The **”permissions”** are divided into 3 parts: * **VISIBLE** allows you to display or not a field in the mobile or web form but it will always be visible on the form configuration page where we are * **EDITABLE** allows the user to modify the value of the field * **REQUIRED** will require the entry of the field in the form to save it ## Saving & Activating functions Once your form is complete, you can save it: ![](/files/O6XuQfjFPyjHIBXW6lWI) “**Activate**” the form will allow users to get the latest [version](/user-documentation/components-concepts-terminology.md#version) of the form: ![](/files/gmfrFCrpkjMxXx3Rnvio) ## Pagination To set up pagination, simply add tabs to the form design. To do this you must click on the "+" in the tab bar. You then simply need to drag and drop the fields into the appropriate tabs. You can change the name of a page by clicking on the corresponding tab. In the advanced settings of the form, an option allows you to define whether "moving to the next page is possible in data validation". If this option is checked, users will be able to freely navigate the form. Otherwise, the current page must be valid (all required fields are completed, email addresses are correctly formatted, etc.) in order to move on to the next page. Navigation is therefore done in a linear manner. It is no longer possible to skip pages, you must use the buttons to go to the next page. ### **To know** * Page names are limited to 50 characters. That said, it risks being shortened if it is too long. We advise you not to exceed 20 characters. * The number of pages is limited to 25 per form. * The paging system works on the web, iOS and the Android app. * The data validation option per page is set at the form level and not page by page (which is different from what existed on page breaks). ## Settings A Daxium-Air form can have several options directly accessible in the form designer, organised into the following sections. ### General information | Setting | Description | | --------------- | -------------------------------------------------------------------------------------------------------------------------------------- | | **Form name** | The name of your form | | **Icon** | Visible on mobile and in the Web platform under Submissions. Optional and purely aesthetic. Recommended size: 25x25 px (PNG supported) | | **Color** | Only visible in advanced options for certain features | | **Description** | Describes what the form is used for | | **Tags** | Keywords to help find the form in a list | ### Data representation | Setting | Description | | ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Customized title** | Simplified representation on card tabs | | **User assigned to the form** | Defines which user must act on the form. Assignees receive real-time updates to their files. See [Workflow & Assignation](/user-documentation/build/building-forms/workflow-and-assignation.md) | | **Default location** | Sets the native position for each file creation on mobile. Can be set to native position (GPS coordinates), a location field, or a formula field of location type | | **Default image** | Defines which image represents the form in the representation view and mosaic view | | **Functional Status** | Applies a color border in [Mixed View](/user-documentation/use/views/mixed.md) (web) and My Cards (mobile) via a color-coded list. If a [workflow](/user-documentation/build/building-forms/workflow-and-assignation.md) is configured, the functional status is based on it | ### Advanced settings | Setting | Description | | ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **First level form** | Hides or displays the form on mobile. Used when the form is filled via a relationship field in another form | | **Restrict access to the form** | Blocks access for all users. Access must then be granted via a [group](/user-documentation/build/managing-users/groups.md). Admin users are never affected by this restriction | | **Duplication of submissions** | Restricts which fields are copied when a submission is duplicated | | **Last active version** | Reverts the form to its last active version, undoing any unsaved changes | ### Task Template Enabling this option defines the form as a [task](/user-documentation/use/tasks.md) template. The following additional settings become available: | Setting | Description | | ------------------------------------- | ------------------------------------------------------------------------ | | **Start date** | The form field used as the task start date (must be a date + time field) | | **End date** | The form field used as the task end date (must be a date + time field) | | **Delay period** | Defines how long after the end date a task is considered completed late | | **Fields accessible during creation** | Fields that must be filled in when creating the task in the back office | --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://www.center.daxium-air.com/user-documentation/build/building-forms/general-concepts.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.