10,730
edits
Important: Deprecating old WebView — Publish failed error
Releases/Spring 2022: Difference between revisions
Jump to navigation
Jump to search
→Reuse answers more effectively
| Line 35: | Line 35: | ||
The reuse answers feature is already available for quite some time. When answering a questionnaire, inspectors can load answers from an earlier inspection so that they don't have to enter the same information again. In this release, questionnaire designers gained a new tool for defining which answers should be offered to the inspectors for reuse. We have introduced a new set of rules called '''On Init'''. These are executed before a questionnaire instance is created. They can be used to define additional variables which can be used in the reuse fetch. This can ensure that inspectors can select from a relevant list of answered questionnaires. | The reuse answers feature is already available for quite some time. When answering a questionnaire, inspectors can load answers from an earlier inspection so that they don't have to enter the same information again. In this release, questionnaire designers gained a new tool for defining which answers should be offered to the inspectors for reuse. We have introduced a new set of rules called '''On Init'''. These are executed before a questionnaire instance is created. They can be used to define additional variables which can be used in the reuse fetch. This can ensure that inspectors can select from a relevant list of answered questionnaires. | ||
=== Disable immediate filtering in Result Viewer === | |||
Before this release, when filtering the questionnaires in the viewer, the changes in the filter applied immediately, refreshing the list of displayed questionnaires. When setting up an elaborate filter in combination with a large number of questionnaires, this sometimes resulted in a sluggish experience. With this release, you have the option to disable automatic searching, set up your filter, and then click '''Search'''. | |||
=== Export with question labels, not IDs === | |||
When exporting answered questionnaire from the Result Viewer, you can now select what to use as table header: | |||
* Use '''Question name''' to use the logical name (ID) of the question. This option is particularly useful if you want to further process the data electronically. | |||
* Use '''Question label''' to use the actual question label. Use this option to create more human-readable reports. | |||
=== Compress selected questionnaire fields === | |||
If you create a very large questionnaire on the Salesforce backend, you can run into maximum field size limitation. To help with this problem, you can compress the largest fields of the questionnaire template: | |||
{| class="wikitable" | |||
! Entity (object) || Compressed fields | |||
|- | |||
| resco_questionnaire || resco_rules, resco_styles, resco_reusefetch, resco_autoreport, resco_localization, resco_reportingproperties, resco_layout | |||
|- | |||
| resco_questionnairegroup || resco_rules, resco_repeatconfig, resco_localization, resco_reportingproperties, resco_layout | |||
|- | |||
| resco_question || resco_rules, resco_localization, resco_reportingproperties, resco_layout | |||
|} | |||
This feature is currently available as a beta, for questionnaires with full template dependency, on the Salesforce backend. To enable compression in the Questionnaire Designer, select the top-level element of a questionnaire template and check '''Compress properties'''. | |||
=== Additional fields for JSON serialized answers === | |||
When JSON storage is enabled, all answers are saved to a single field. If your questionnaire is very large, the field can be quite large as well. On Salesforce, the maximum length of a text field is 131,072 characters. | |||
For Salesforce backends, we have enabled two additional fields for storing the JSON string, thus tripling the maximum size. This feature is available as a beta. No configuration necessary. | |||
=== Default value for Image/Media question === | |||
You can now define one image/media file/document that's used as the default answer. | |||
One of the less obvious implications of this feature is that it enables document roundtrip. For example, you can include a Microsoft Visio diagram in your questionnaire. The inspector taps the document and edits it in an external application. Once saved and done, the modified document automatically replaces the original default. Document roundtrip is available on Windows and Android apps. | |||
== Document filters for Salesforce == | == Document filters for Salesforce == | ||