Response consistency check - test version
- 1.1 Changes in the SCU
- 1.1.1 Predial
- 1.1.2 Questionnaire versioning
- 1.1.3 Automatic archiving
- 1.1.4 Results modification lock
- 1.1.5 Reports
- 1.1.6 Response consistency check - test version
- 1.1.7 Variables in e-mailing
- 1.1.8 The information on the volume of e-mail messages planned for sending
- 1.1.9 Database filtering using the LIKE command
- 1.1.10 Device support upgrades
- 1.1.11 Batch file save in the control
- 1.1.12 GPS results on Google maps
- 1.1.13 Empty file send lock
- 1.1.14 Emergency uploading of encrypted MOBI files
- 1.1.15 Linux installation
- 1.1.16 Windows x64
- 1.1.17 Project cloning
- 1.1.18 Embedded questionnaires
- 1.1.19 JS link to the questionnaire
A test version of the module intended to perform consistency check of responses saved in the interview has been introduced. This allows to check whether changes introduced during the validation stage are compatible with the questionnaire script rules.

An algorithm reprocesses the interview, examines new responses and accordingly determines which question lacks a response or on the contrary, which questions no longer needs one. Now the results include also the information about erroneously selected cafeteria, which will become unavailable after changes. The module detects erroneous configurations of responses which would cause questionnaire loops, preventing it from being completed. Also the function indicates errors when validating data on a specific screen (e.g. forced summing to 100%). If changes result with an interview status change, a relevant message will be generated as well.

Unfortunately, at the moment the algorithm is not suitable for questionnaires using random values generated in the script for cafeteria or questions filtering. However there are no problems with random order of screens in loops or in folders.