Inspections: Difference between revisions

Jump to navigation Jump to search
1,018 bytes removed ,  1 June 2022
Line 145: Line 145:
== Performance considerations ==
== Performance considerations ==


When you deploy Resco Inspections in large projects without considering performance, your users may experience performance degradation. Learn about the possible problems in advance and set up your questionnaires to mitigate the risks.
When you deploy Resco Inspections in large projects without considering performance, your users may experience performance degradation. Learn about the possible problems in advance and set up your questionnaires to mitigate the risks: see the [[best practices for deploying Inspections]].
 
=== Sync: upload takes too long ===
 
Inspectors in the field who perform many large inspections regularly may sometimes experience the problem that the upload phase of synchronization takes too long, particularly if the network isn't too good. Increasing the dependency level to full as described above can help, because the amount of data for upload is reduced. Additional savings can be accomplished by changing how questionnaire answers are stored and uploaded.
 
Edit your questionnaire template and on the [[Questionnaire_Designer#Properties_pane|'''Properties''' pane]], configure the '''Answer Storage''' to select how should the answers be stored.
 
* '''Records''': This is the default option. Each answer is transferred as a single record during synchronization. This may make synchronization slower, but ensures the best compatibility with the backend servers and allows you to leverage existing tools to visualize the data.
* '''JSON''' or '''Compressed JSON''': These options offer improved synchronization performance, however, not all tools understand JSON.


== Tip: Migrating inspections between environments ==
== Tip: Migrating inspections between environments ==

Navigation menu