In this article
When launching a survey in the Test database, you have the option to allow access by external users so they can test the Survey - .
Figure 1 - The Launch Options dialog for the Test database
When you select Enable External Test, the survey files will be made available at the deployment servers and the link for the test survey will be displayed at the bottom of the task execution log. The link contains a cryptic key to prevent unauthorized access to the test survey - - see below.
Figure 2 - Example of the link on the task log
The external test link is also displayed on the Survey Overview page (go to General for more information). This page also contains a field indicating whether the production and test databases are in sync; i.e. have the same "last modified" timestamp. This is to tell the author whether the people testing the survey are seeing the same version of the survey as that which is currently online.
Note: The maximum limit for the number of external users that can access the test database to test the survey is 100. The "External Test Response Limit" is displayed at the bottom of the Interview Progress page. Note that only Web interviews are counted against this limit; not RDG responses.
Enabling Databse Encryption
Note: Database encryption is a company add-on and is subject to payment. If your company does not have the add-on, then the option will not be available in the Launch Survey page.
When launching a survey in the production database, the Enable Database Encryption option is available. If you select this option, the production survey database will be encrypted. The data that will be encrypted will include Response, Respondent and Hub data.
Note that it is not possible to change the encryption state of a previously launched database; once a database is launched, if you wish to change the encryption state you must create a new database.
If the Enforce Encryption option is set for your company (check with your Forsta company administrator) then the Enable Database Encryption option will also be available when launching test databases.
Errors
When you launch a survey Authoring checks all scripting code that you have added. If any script errors are found, then the launch is aborted and a frame opens below the task pane. This frame lists all the errors that have been found, and indicates where in the survey the error is located - .
Figure 3 - Example of a script error frame with an error link
Click the link in the error pane to open the appropriate question at the tab containing the scripting error.
You can also view runtime errors in the frame. These could be script, page or component errors that occur during runtime. The list is searchable, and includes links to the page, script or component causing the error.