Survey
Survey is the main module of the three mentioned and it contains all the information that can be useful for decision-making purposes.
In the survey module, all fields related to email sending cannot be changed because the notification email can only be sent upon survey creation.
Below is the list of available fields and their meaning for the Survey module:
Field | Description |
Template | Text field auto-populated with the survey template related to this survey. |
Name | The text field that is used to name the survey.
This field can be selected in the dashboard model to verify the survey results.
It will be inherited from the survey template and can be changed. |
Model Alias | A survey can be related to another model which can trigger the survey creation.
It can be changed. |
Model Id | The ID of the model related to the survey.
It can be changed. |
Intro Notes | This field will be displayed at the beginning of the survey before all the questions. |
Final Notes | This field will be displayed at the end of the survey after all the questions.
It will be inherited from the template and can be changed. |
Description | Internal Description field for the surveys. |
Is Anonymous | If set to Yes, can permit anonymous answers by recipients. |
Show Submit in All Pages | If set to Yes, it allows to show the “Submit” button on all survey pages if provided.
It will be inherited from the template and cannot be changed. |
Expires in Days | Numerical field which sets a time of expiration for the survey. The count starts from the moment the survey is created. Once the survey expires, the main status will be changed automatically to “Expired” and the flag “Is Expired” will be set to Yes.
It will be inherited from the template and can be changed. |
Expires in Hours | Numerical field which sets a time of expiration for the survey. The count starts from the moment the survey is created. Once the survey expires, the main status will be changed automatically to “Expired” and the flag “Is Expired” will be set to Yes.
It will be inherited from the template and can be changed. |
Expires in Minutes | Numerical field which sets a time of expiration for the survey. The count starts from the moment the survey is created. Once the survey expires, the main status will be changed automatically to “Expired” and the flag “Is Expired” will be set to Yes.
It will be inherited from the template and can be changed. |
Is Expired | If set to Yes, it indicates that the survey has expired. |
Fronted Visibility | It allows us to enable the surveys for the frontend portal (portal for unregistered users).
It will be inherited from the template and cannot be changed. |
Send Email | If set to Yes, it allows to send a mail on survey creation.
It will be inherited from the template and cannot be changed. |
Groups | Multiselect fields where you can choose the groups who should have visibility on this survey.
CREATION: Upon survey creation, it will be used to send an email to all users in the specified group (assuming all other email fields are correctly configured).
CREATION/EDIT: You can modify this field to enable or disable the visibility of the survey for a specific group. It is also used to allow using the survey as a filter in the “Charts” tab within the dashboard module.
It will be inherited from the template and can be changed. |
Users | Multiselect fields where you can choose the users who should have visibility on the created survey.
CREATION: Upon survey creation, it will be used to send an email to all users selected (assuming all other email fields are correctly configured).
CREATION/EDIT: You can modify this field to enable or disable the visibility of the survey for a specific user. It is also used to allow using the survey as a filter in the “Charts” tab within the dashboard module.
It will be inherited from the template and can be changed. |
Send Emails | If set to yes, can permit email sending on survey creation.
NOTE: All other email fields should be configured to allow sending mail. |
Mailbox | By this field, you can choose a specific mailbox to use for sending emails.
It will be inherited from the template and cannot be changed. |
Use Template | If set to “ON”, it enables “Email Template ID” to be used for email sending on survey creation.
It will be inherited from the template and cannot be changed. |
Email Template Id | With this field, you can select a preconfigured email template to be used in emails sent on survey creation.
It will be inherited from the template and cannot be changed. |
Subject | This field will be displayed only if the “Use Template” field is set to “OFF”, and it is used to set a subject for the email sent on survey creation.
In this field, you can use the variables “users” and “survey” to create a dynamic template.
Example:
It will be inherited from the template and cannot be changed. |
Email HTML Body | This field will be displayed only if the “Use Template” field is set to “OFF”, and it is used to set a mail body for the email sent on survey creation.
In this field, you can use the variables “users” and “survey” to create a dynamic template.
Example:
It will be inherited from the template and cannot be changed. |
Status | With this field, you can enable or disable a survey.
It will be inherited from the template and can be changed. |
Results | Is a relation grid that shows all the survey results in progress or completed ones. You can also directly add a Result by clicking on the “Add Result” button. |
Emails | Is a relation grid for all the emails that has been sent for this survey to users and groups on survey creation. |
Here Results and Email grid related to the survey:
Manual Using
By clicking on the “Add Result” button on the “Results” relation grid, you can add a new result for a survey, and you can also relate it to a specific user.
Anyway, no email will be sent to recipients. The email for the survey is only sent upon survey creation.
The available fields are the following:
Field | Description |
Template Id | Auto-populated field with the ID of the survey template related to this survey. |
Survey | Auto-populated field with the related survey name. |
Username | A Select field with all the users, where you can choose the user who is going to fill out the survey. |
Company Id | Auto-populated field with the company of the selected user. |
Status | Select the field with the status of the result with values: In progress, Completed, Expired. |
After the result creation, an operator can compile the survey on his own by clicking on the “Fill Out” button at the end of the “Result” record:
In this case, the Result creation and the survey filling from the main survey module are exclusive prerogatives of Deepser internal users.
Default Using
Generally, the survey module relies on the End-User portal, as it allows for the completion of its questions.
Normally, within the email sent during the survey creation phase, a direct link to the portal is included, enabling access to the survey. Upon accessing the survey, a “Result” record is automatically created and associated with the respective survey.
Additionally, it is possible to access the survey management section directly from the End-User portal menu:
NOTE: In the End-User portal, the grids related to the surveys exclusively display records of type “Result”. Therefore, to view a new survey, users are required to go through the email sent during the survey creation phase. Specifically, by clicking on the survey link in the email, the “Result” record will be created and consequently can be viewed in the grid.
By the backend, a user can edit, change, or add a new visualization grid for the survey module in the end-user portal by simply accessing System > Portal > Survey.
