# Tasks

## Tasks

### Introduction

Creating tasks first requires configuring the form so that it is compatible with this functionality. The operation is very simple, it simply consists of providing our form with two date/time fields in order to be able to locate it in time, then only one box remains to check to confirm that it can be used within the framework of creating tasks.

### Configuration

1. Insert two “Date” fields in “Date/Time” format, which we will name **date\_start** and **end\_date**
2. In the form settings, check “Allow the creation of tasks from this form”
3. Select created fields in red drop-down menus
4. Save then activate your form once the settings are complete

![](/files/pyToSub3gaOeCF0Qmp3z)

**NFC:** Requests the reading of an NFC tag in order to perform the task.

**Start date:** When starting the task on the mobile, the following field will be automatically completed.

**End date:** When the user finishes entering the form, the field will be automatically completed before sending.

**Deadline:** Allows you to include a deadline before the task is considered late. If we set it to 1 hour or if the task starts at 3:00 p.m. and ends at 4:00 p.m., then the overdue deadline will be pushed back to 5:00 p.m.

**Fields accessible during creation:** This defines the form fields that can be pre-populated when creating the **task**.

Then you will find the option "Task template" active in the view listing the forms:

![](/files/hEiWRD1WNHGJOmuAy7FE)

**Warning**: Tasks are incompatible with workflows and broadcasts. These are indeed three distinct methods of sending Submissions.

### Usage

***

## Importing tasks

Tasks can be imported in bulk using a CSV file whose structure is defined below.

### Columns to configure the task

Task import requires the use of 6 columns to define it:

* **Submission#structure\_id**: this column allows you to choose the form in which an import is to be carried out. the identifier (structure ID) is for example at the end of the form designer URL. (.../structures/builder/XXXX).
* **Submission#userEmail**: This e-mail allows you to identify the user who created the form.
* **type**: here you have the choice between a simple task and a recurring task. As it currently stands, you can only import simple tasks. You must therefore set the value "simple"
* Start and end dates of the task: they must be entered in ISO 8601 format. Example: 2018-04-30T17:00:00+02:00
  * **start\_date**: this is the expected start date of the task
  * **due\_date**: this is the expected completion date of the task
* **user\_email**: this column allows you to assign the task to a Daxium user. You must write the user's email in this column. Please note, you cannot assign tasks only to mobile users.

### Columns to configure the associated form

Each task must be associated with a form. To do this, you must first specify which form model you are working on. You must therefore include a **Submission#structure\_id** column.

This column must be populated with form identifiers compatible with task creation. This identifier can be found, for example, at the end of the form designer URL. (.../structures/builder/XXXX).

You can then fill in the fields of the form. To do this, simply do as in a file import, but prefix the columns with **Submission#**. For example, to define the owner of the form (which is mandatory), you must create a **Submission#userEmail** column. To fill a list using external identifiers this gives: **Submission#ListSystemName#external**.

This way you can fill in all the fields of a form, even if they do not appear in the list of fields accessible when creating a task.

An example of a task import CSV is available at [this link](https://doc.daxium-air.com/hc/fr/article_attachments/360003904053/tasks.csv).

### Setting up the import

Once your CSV file is ready, you must upload it to Daxium-Air. To do this, you must go to the "Tasks" section, then click on "Import".

All you have to do is choose your CSV file and determine the separator you use (by default it is the semicolon in France and the comma for most other countries).

The import takes place in the background. You will be notified by the notification bell when it is finished.

### Error handling

When your import is finished, if an error prevented one or more files from being saved, you will have a return in a CSV file. This file is accessible from the notifications bell at the top right of your screen.

This will allow you to understand what went wrong and how to correct the problem.

![](/files/JoGz83frsxSVBHgNHaOb)


---

# 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/use/tasks.md?ask=<question>
```

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.