The query export will run in the background. When it is finished, the platform posts the file in the user’s private folder, which must be enabled, and notifies you by e-mail when the process is complete. This exported file necessarily must contain the following columns:

• Request: number of the request;
• Description: description of the process;
• Status:  status of the request;
• Requester registration: registration of the requester;
• Requester: name of the user that is the requester;
• Location: activity in which the request is;
• Person in charge: name of the person responsible for the activity in which the request is;
• Start: date on which the request was initiated;
• End: date on which the request was completed (if completed).

The columns above are default and always appear at the beginning of the exported file. Data related to the activities and forms can also be added to this file. However, the order in which these columns are displayed can be changed, depending on the amount of requests, activities moved and form fields defined in the query parameters.

When the Add activity data option is checked for the ongoing activity, the person currently responsible for it is displayed, and the completion date column is left blank. Only the activities through which some query request went through will be listed. The other activities of the process will not be displayed. The exported file will include data for the movement of activities of the processes selected for the query. Only moved activities will be included. Therefore, the movement of the request can generate a greater number of columns. Each activity is represented by two columns:

• Activity - [Name of the activity] - Person in charge: Person in charge name.
• Activity - [Name of the activity] - Completion: Date of movement.

When the Add form data option is checked, the file adds the fields of the forms related to the processes selected for query. The form fields are included in the exported file for each process found, forming a cascade of information, and the order of the columns for each form depends on its storage model.

• If the form is stored in a single table: fields are displayed in alphabetical order in the file columns;

If the form is stored in multiple tables: the fields are displayed in the same order that they were added to the form. In the first version, they will be displayed in the same order they were added when the form was created. In subsequent versions, each new field added to the form will be included at the end of the file.

Available options:

• Add activity data When checked, it displays the name of the person in charge and the completion date of all finished process activities. If you check this option, you will not be able to view the query results on the screen, only their export will remain enabled. For the ongoing activity, the person currently responsible for it will be displayed, and the completion date column will be left blank. Only the activities through which some query request went through will be listed. The other activities of the process will not be displayed.

• Enter request deadline information:

• Add form data: When checked, the data entered in the form fields of each request are included in the query results. If you check this option, you will not be able to view the query results on the screen, only their export will remain enabled.

• Add multiple records: When checked, data from the form child fields are also added. This option is only enabled if the Add form data option is checked.

• Group multiple records: When checked, the data from the form child fields are grouped into a single cell in the worksheet. This option is only enabled if the Add multiple records option is checked.

The query export will run in the background. When it is finished, the platform posts the file in the user’s private folder, which must be enabled, and notifies you by e-mail when the process is complete. This exported file necessarily must contain the following columns:

• Request: number of the request;
• Description: description of the process;
• Status:  status of the request;
• Requester registration: registration of the requester;
• Requester: name of the user that is the requester;
• Location: activity in which the request is;
• Person in charge: name of the person responsible for the activity in which the request is;
• Start: date on which the request was initiated;
• End: date on which the request was completed (if completed).

The columns above are default and always appear at the beginning of the exported file. Data related to the activities and forms can be added to this file. However, the order in which these columns are displayed can be changed, depending on the amount of requests, activities moved and form fields defined in the query parameters.

When the Add activity data option is checked for the ongoing activity, the person currently responsible for it is displayed, and the completion date column is left blank. Only the activities through which some query request went through will be listed. The other activities of the process will not be displayed. The exported file will include data for the movement of activities of the processes selected for the query. Only moved activities will be included. Therefore, the movement of the request can generate a greater number of columns. Each activity is represented by two columns:

• Activity - [Name of the activity] - Person in charge: Person in charge name.
• Activity - [Name of the activity] - Completion: Date of movement.

When the Add form data option is checked, the file adds the fields of the forms related to the processes selected for query. The form fields are included in the exported file for each process found, forming a cascade of information, and the order of the columns for each form depends on its storage model.

• If the form is stored in a single table: fields are displayed in alphabetical order in the file columns;

If the form is stored in multiple tables: the fields are displayed in the same order that they were added to the form. In the first version, they will be displayed in the same order they were added when the form was created. In subsequent versions, each new field added to the form will be included at the end of the file

This documentation is valid as of the 1.6.5 update - Liquid. Previous updates may contain different information than what you see on your platform.