# Daxium-Air Glossary ## API The Daxium-Air API is a REST interface that lets external systems read and write submissions, lists, users, and reports programmatically. ## ASSIGNMENT Assignment allows you to assign one or more submissions to a user via a workflow, so the user receives the submission on their mobile. ## AUTOMATION An automation is an action (send a notification or an email, generate a report, change the value of a field, etc.) triggered automatically when a chosen event occurs and/or under certain conditions. Automations are defined within a form and therefore only affect the forms of this form. ## BACK-OFFICE The back office is the [Daxium-Air](https://www.daxium-air.com/) web platform connected to your customer account, where you find your customized environment. Depending on your user rights, you can configure forms, analyze data, create submissions, etc. ## BROADCAST The distribution of submissions on mobile is a way of being able to share data to meet one or more conditions with different groups of users (incompatible with the assignment and therefore with workflows). ## MAP LAYER It is possible to display your submissions on a map using their positioning. Map layers can enrich these views of lines and shapes with information from your operations. ## CONDITION A Condition is a rule on a field or lists of fields within an associated values. For the condition to be satisfied, all field values must be validated on the field on which condition was applied. ## CUSTOM TITLE This option is similar to the representation but in a more limited way, because it includes the data on a single line in the tabs of your cards but also on the dots in map view. By default, the value displayed in the tab corresponds to: submission No. xxxxx ## DASHBOARD A dashboard is a control and management tool. It is a visual representation of important information and performance indicators on a single screen through graphs, charts, etc. This makes it possible to measure the performance of a company and evaluate the achievement of objectives. ## FIELD A field has a predefined type (number, text, email, photo, file, etc) which allows you to indicate the type of information that the user must enter in their submission. The fields are configured in the form. ## FIELD PERMISSIONS In a form, the permission of a field is used to configure 3 parameters: is the field visible to users? Can the field be modified? Is the field required? ## FORM A form is a digital tool made up of a series of fields to be completed, which you have configured yourself on Daxium-Air according to your needs, in order to collect data. ## FUNCTIONAL STATUS The elements of a list can have a color. When this list is used in a form and this list is configured in the form parameters as the functional status, this allows the cards to be colored in the card view and the mixed view, for example. ## GROUP A user group is a workspace-scoped collection of users sharing the same access rights and permissions on Daxium-Air web and mobile. Each workspace defines its own groups; users gain access to a workspace through their group memberships. ## GROUP PERMISSIONS This menu lists all the permissions that are available by license type (administrator, mobile, web contributor or web reader) and it is possible to add permissions to user groups. Thus, a user combines the permissions of his license and his group. ## INTEGRATION An integration is a connection between Daxium-Air and an external system to exchange data, built using webhooks, the API, planned exports, or no-code connectors like Make. ## LICENSE The capability tier attached to a User — Administrator, Mobile, Web Contributor or Web Reader — that determines which actions the User can perform. A User's effective rights combine their License with the Permissions granted to their Groups. ## LIST A reusable, optionally hierarchical set of values referenced by list-typed Fields. Each item may carry a label, an external id, a Functional status color, a URL and an image, and a List supports up to 100,000 items. ## LISTING MODE When configuring a Report, if **Listing mode** is checked, the Report will include several submissions. Otherwise, the Report will be based on a single submission. If **Listing mode** is unchecked but the submission has one or more Relations, only the information from the parent submission appears. To include all the information (parent and children) in the Report, check **Listing mode**. ## MASS CHANGE This action can only be carried out on the web to modify the field(s) of the selected submission(s). This only works on cards in the latest version of the form. ## MIGRATION Migration is the action of moving submissions from an earlier version of a form to a later one. When a form is modified and re-activated, a new version is created; existing submissions remain in their original version until migrated. See [Migrations](/user-documentation/build/building-forms/migrations.md) for the full workflow. ## MODEL A Model is a Word or Excel file used as a template, that can contain the information from one or more submissions. The result is a Report. ## NFC TAG An NFC tag allows, for example, to automatically fill in the fields of a form or to open a form. ## PRE-FILL Pre-populating data saves your agents time. Each Field can be made pre-fillable; to do this, enable the **Pre-fill** option in the Advanced options. Users, on mobile or web, can then fill in the information they want and each submission created subsequently will contain this information. ## REPORT A report is a file (Word, Excel, or PowerPoint) generated by Daxium-Air by merging submission data into a Model. Reports can be generated manually from a submission, automatically on a trigger, or on a recurring schedule. A report based on a single submission uses the submission's own data; a report in Listing mode aggregates data from multiple submissions. ## RELATION A relation field allows you to link two forms together in one direction. The one that contains the relation field is considered the main form, often called parent, and the one that is covered by the relation can be called a sub-form, or child form. ## REPRESENTATION The representation of data allows you to customize the preview of a submission on the web as well as on mobile. It is recommended to systematically configure the representation of the form. This feature is particularly useful during relations. ## SCHEDULED EXPORT Scheduled exports allow you to connect Daxium-Air and Power BI in order to update dashboards (up to 4 times per day). ## SHORTCUT This web functionality offers you a way to optimize your navigation on Daxium-Air by allowing you to directly access the elements consulted on a recurring basis (shortcut to a customized application, parameters, forms, submissions, dashboard, etc.). A shortcut can be visible to all users, or one to one or more groups. ## SUBMISSION A submission is a form with at least one field completed by a user, via the web platform or the mobile app. Your submissions form the dataset you produce, query and report on. ## SUBSCRIPTION A bundle of Licenses purchased by your organisation and allocated to your Users — for example, 50 Mobile Licenses and 10 Web Contributor Licenses. ## SYSTEM NAME In a form, the system name of a field is different from the label because it does not appear for mobile users. The system name is useful for configurator (administrator users), particularly when linking with Word, Excel or even Power BI reports. It is mandatory to give a unique system name. Special characters other than "\_" are not authorized. We strongly recommend using one of the following nomenclatures: *1. system\_name* *2. systemname* *3. SystemName* *4. System\_Name* ## TASK If the "Allow creation of tasks from this form" is checked, then it will be possible to view each submission in the calendar view, on the web as well as on mobile. Attention: Tasks are incompatible with workflows and broadcasts. ## USER A Daxium-Air user has an identification email, a password as well as a type of license in order to connect. It can belong to one or more user groups. ## VERSION Every time a form is edited and reactivated, Daxium-Air creates a new version of it. Existing submissions stay on the version they were created in until they are migrated. For example, if you add a field to a form, existing submissions will not show that field until they are migrated to the new version. See [Migrations](/user-documentation/build/building-forms/migrations.md) for the full workflow. ## WEBHOOK A webhook allows you to automatically send submissions to HTTP endpoints in JSON format at certain points in the submission lifecycle. Webhook configuration is done at the automation level. ## WORDING In a form, the wording of a field is its name, that is to say what will appear when a user fills out their form, on mobile or on the web. ## WORKFLOW A Workflow defines the life cycle of a submission through states. Each state can route the submission to a User, who receives it on their mobile to continue work, so a team can take turns on the same submission as it moves between states. ## WORKSPACE A workspace is a dedicated Daxium-Air environment containing its own forms, lists, reports, submissions, groups, and apps. A user can work in several workspaces. --- # 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/components-concepts-terminology.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.