General tab (survey task properties)

Option	Description
ID	Indicates the default ID number assigned to this survey task by CCA.
Name	Specifies the survey task's name.
Description	This field can be used to provide a description of the survey task when the survey is added to WebProd with CCA.
Path	Indicates the path to the survey task's *.QES file. That is, the questionnaire file here specified will be updated continuously by CCA as its fieldwork progresses, adding new interviews etc.
Work directory	Indicates the path to the survey task's work directory. When audio recordings are made, this is where the audio files are saved.
Target sample size	Specifies the survey task's target sample size, that is, its target number of successful interviews to be completed in the field. Note that if a range has been set, using the `min. target` and `max. target` columns in the quotas view, then you cannot enter the target here; you will need to go into the `quotas` view to change it.
Keep incomplete interviews	If this option is selected, incomplete interview data is not discarded, whatever the call result. For example, if the interview is refused, out of quota, etc., the data will be kept. Note that this option is over-ridden by the questionnaire routing "go without saving": in other words, if "go without saving" routing is enacted during an interview, the interview is not saved. This option applies to any interviewing mode; prior to version 5.3.0, it applied only to CATI and Web interviews. Note: you can change this option during fieldwork.
Interview storage	Determines the format in which interview data will be stored. This option is available only when you first define the survey task. Once your survey is initialized, the option cannot be changed. QES file: Interview data for this survey task will be stored in the QES file. SQL Server (legacy format): Interview data will be stored directly in SQL databases (surveys db) instead of the QES file. This will be in an older SQL format, for compatibility with other products. SQL Server: Interview data will be stored directly in SQL databases (surveys db) instead of the QES file, in a new, more efficient format. Note: at the end of fieldwork, interview data can be copied back into the QES file by right-clicking the survey in the tasks window, and selecting Synchronise interviews into qes file.
Survey progression (CATI/CAPI)	Allows you to set the navigation options available to the agent during CATI and CAPI surveys. Forward move only: CATI and CAPI agents will only be able to move forwards through the interview (the back button is deactivated). Backward and Forward: Standard mode. Agents will be able to go backwards and forwards within the questionnaire. Authorise jump backward: Allows agents to select an earlier question in the questionnaire tree and go directly to it, using the `go to question` button in the agent's navigation bar. Authorise jump anywhere: Agents will be able to select any question in the questionnaire tree (before or after the current question) and go directly to it, using the `go to question` button in AskiaVoice's navigation bar.
Allow feedback (CAWI only)	Note: in order to use this feature, the survey feedback tool must be configured in your CCA installation. For details on how to set it up, see the Knowledge Base article survey feedback reader tool. This option applies to CAWI (Web) surveys only. It allows CAWI testers and/or respondents to submit feedback about the survey (they do so by clicking `send feedback` at the bottom right corner of the survey screen). Never: Testers and respondents cannot submit feedback. Only test interviews: The `send feedback` button is available only during test interviews (so only testers can submit feedback). All interviews: The `send feedback` button is always available (so both testers and respondents can submit feedback). When a tester or respondent clicks the `send feedback` button, he or she sees the following dialog: He or she can specify the category of their comment (`typo`, `problem with layout`, `suggestion` or `other`), and enter a comment. He or she can also, optionally, enter an email address, thus allowing the survey scripter to reply, for example, to ask a follow-up question or to notify the commenter when the issue has been fixed. The following dialog then appears, where the tester or respondent can highlight or black out specific areas of the screen to indicate where the subject of their comment (e.g. a typo) is located. The highlight and blackout tools produce the following effects: Note that both highlight and blackout can be used on the same screen. The submitted feedback is stored in the Statistics SQL database, in the Statistic_SurveyFeedback table. This information will be available through a tool linked via the API.
Field list	Specifies which of the Askia CCA system fields and sample list fields you wish agents to be able to view.
Don't load interviews started before	This option, if selected, allows you to specify a date, which will act as an interview filter. Interviews started outside of this filter (i.e. before the specified date) will not be loaded, and will be ignored for quotas. Interviews started before this date will not be loaded. In the adjacent drop-down list, you can specify what should happen when a callback for such an interview comes up (see the option callbacks or appointments for these interviews, described below).
Callbacks or appointments for these interviews should	This option is used in conjunction with the option don't load interviews started before, as described above. It determines how AskiaField will handle appointments or callbacks for interviews that were started before the specified date. You can choose not to conduct the appointment/callback at all, use the original interview, or use a new (empty) interview.

Option

Description

Indicates the default ID number assigned to this survey task by CCA.

Name

Specifies the survey task's name.

Description

This field can be used to provide a description of the survey task when the survey is added to WebProd with CCA.

Path

Indicates the path to the survey task's *.QES file. That is, the questionnaire file here specified will be updated continuously by CCA as its fieldwork progresses, adding new interviews etc.

Work directory

Indicates the path to the survey task's work directory. When audio recordings are made, this is where the audio files are saved.

Target sample size

Specifies the survey task's target sample size, that is, its target number of successful interviews to be completed in the field.

Note that if a range has been set, using the min. target and max. target columns in the quotas view, then you cannot enter the target here; you will need to go into the quotas view to change it.

Keep incomplete interviews

If this option is selected, incomplete interview data is not discarded, whatever the call result. For example, if the interview is refused, out of quota, etc., the data will be kept.

Note that this option is over-ridden by the questionnaire routing "go without saving": in other words, if "go without saving" routing is enacted during an interview, the interview is not saved.

This option applies to any interviewing mode; prior to version 5.3.0, it applied only to CATI and Web interviews.

Note: you can change this option during fieldwork.

Interview storage

Determines the format in which interview data will be stored. This option is available only when you first define the survey task. Once your survey is initialized, the option cannot be changed.

QES file: Interview data for this survey task will be stored in the QES file.

SQL Server (legacy format): Interview data will be stored directly in SQL databases (surveys db) instead of the QES file. This will be in an older SQL format, for compatibility with other products.

SQL Server: Interview data will be stored directly in SQL databases (surveys db) instead of the QES file, in a new, more efficient format.

Note: at the end of fieldwork, interview data can be copied back into the QES file by right-clicking the survey in the tasks window, and selecting Synchronise interviews into qes file.

Survey progression (CATI/CAPI)

Allows you to set the navigation options available to the agent during CATI and CAPI surveys.

Forward move only: CATI and CAPI agents will only be able to move forwards through the interview (the back button is deactivated).
Backward and Forward: Standard mode. Agents will be able to go backwards and forwards within the questionnaire.
Authorise jump backward: Allows agents to select an earlier question in the questionnaire tree and go directly to it, using the go to question button in the agent's navigation bar.
Authorise jump anywhere: Agents will be able to select any question in the questionnaire tree (before or after the current question) and go directly to it, using the go to question button in AskiaVoice's navigation bar.

Allow feedback (CAWI only)

Note: in order to use this feature, the survey feedback tool must be configured in your CCA installation. For details on how to set it up, see the Knowledge Base article survey feedback reader tool.

This option applies to CAWI (Web) surveys only. It allows CAWI testers and/or respondents to submit feedback about the survey (they do so by clicking send feedback at the bottom right corner of the survey screen).

Never: Testers and respondents cannot submit feedback.
Only test interviews: The send feedback button is available only during test interviews (so only testers can submit feedback).
All interviews: The send feedback button is always available (so both testers and respondents can submit feedback).

When a tester or respondent clicks the send feedback button, he or she sees the following dialog:

He or she can specify the category of their comment (typo, problem with layout, suggestion or other), and enter a comment. He or she can also, optionally, enter an email address, thus allowing the survey scripter to reply, for example, to ask a follow-up question or to notify the commenter when the issue has been fixed.

The following dialog then appears, where the tester or respondent can highlight or black out specific areas of the screen to indicate where the subject of their comment (e.g. a typo) is located.

The highlight and blackout tools produce the following effects:

Note that both highlight and blackout can be used on the same screen.

The submitted feedback is stored in the Statistics SQL database, in the Statistic_SurveyFeedback table. This information will be available through a tool linked via the API.

Field list

Specifies which of the Askia CCA system fields and sample list fields you wish agents to be able to view.

Don't load interviews started before

This option, if selected, allows you to specify a date, which will act as an interview filter. Interviews started outside of this filter (i.e. before the specified date) will not be loaded, and will be ignored for quotas.

Interviews started before this date will not be loaded. In the adjacent drop-down list, you can specify what should happen when a callback for such an interview comes up (see the option callbacks or appointments for these interviews, described below).

Callbacks or appointments for these interviews should

This option is used in conjunction with the option don't load interviews started before, as described above. It determines how AskiaField will handle appointments or callbacks for interviews that were started before the specified date. You can choose not to conduct the appointment/callback at all, use the original interview, or use a new (empty) interview.

Note: we recommend that you ensure the survey task's work directory contain both the task's *.QES file, and its sample list(s) *.lst file(s). This is so that, in case of disconnections between agents and CCA, interview files are saved locally on the agents' machines. Once the agent's connection to CCA is re-established, interview files will be copied to the CCA in the corresponding survey task’s work directory. The next time the administrator starts CCA, it will automatically browse all its survey tasks' work directories, importing any interview files into their respective *.QES files. Storing all the files pertaining to a survey task in its work directory therefore enhances coherency and facilitates the administrator’s management of the CCA.