9,270
edits
Join the Power Platform Masterclass #2 starting April 23
Inspections: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 129: | Line 129: | ||
For example, when displaying a list of available templates for mobile users to choose from, use only active or published templates. Set this up in the view filter. For the sync filter, however, consider also including archived templates if you want to allow the mobile users to view older completed questionnaires. | For example, when displaying a list of available templates for mobile users to choose from, use only active or published templates. Set this up in the view filter. For the sync filter, however, consider also including archived templates if you want to allow the mobile users to view older completed questionnaires. | ||
=== Innovations === | |||
Resco Inspections have a strong focus on innovations to fully leverage modern devices and technologies. | |||
;Inspections with augmented-reality video calls | |||
:Inspectors in the field can initiate a video call to an expert. The recipient can draw instructions straight into the shared video scene. See [[Houston video calls]]. | |||
;Wearables and ruggedized devices | |||
* [[Smartwatch integration]]: perform inspections with a smartwatch and voice control | |||
* [[RealWear]]: a custom version of the Resco app tailored for voice control is available for the head-mounted tablet HMT-1 | |||
* [[Zebra]]: Resco Inspections is certified by Zebra for their TC series of handheld computers | |||
* [[Resco Mobile CRM on HoloLens|HoloLens]]: Perform inspections in 3D. | |||
== 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. | |||
=== Rapidly increasing database footprint === | |||
If you created your Resco Inspections organization some time ago, the default setting used to be that every single answered questionnaire is saved in a self-contained way, i.e., it includes the answers, but also the questions along any possible custom images (logo), business rules, and styles. This approach ensures that even if the original questionnaire template changes, your answered questionnaires are unaffected. | |||
In scenarios where questionnaires are changing frequently and each questionnaire is answered only a limited number of times, this is a valid approach. However, if your inspectors perform hundreds or thousands of inspections every day, you might discover that your database gets full of redundant data. | |||
Use the parameter '''Dependency Level''' in the [[Questionnaire_Designer#Properties_pane|properties of a questionnaire template]] to control this behavior. | |||
* '''None''': This is default value. Questionnaires are self-contained, at the cost of increased database footprint. | |||
* '''Images''': In this case, static images of the questionnaire template (such as the logo) are not included in each answer. | |||
* '''Full''': Save only the answers. Static images, questions, rules, and styles are not included; instead, they are replaced with a reference to a questionnaire template. This option is recommended if your questionnaires rarely change and it is only available for versioned questionnaire templates. | |||
: <small>Using versioned templates means that old template versions gain the archived state. Sometimes, the sync filter for the Questionnaire entity is configured to exclude archived templates. If you attempt to view old answered questionnaires (that use an archived template with medium or high dependency level) in the app in offline mode, you may encounter the ''Questionnaire template not found!'' error. In this case, consider modifying the sync filter to make archived templates available in the offline mode.</small> | |||
Another complementary option is saving your images in external cloud document storage, rather than in the database. This behavior is configured on the Properties pane for images in the parameter '''Storage Entity'''. Cloud document storage is often much cheaper than databases. Resco Inspections supports third-party document storage by Box, Dropbox, Google Drive, OneDrive, and SharePoint. | |||
=== Slow questionnaire loading time === | |||
If your complex questionnaire templates include many On Change rules, app users may experience slow performance when they open the questionnaire in the app. This issue affects particularly older devices. | |||
Edit your questionnaire template and on the [[Questionnaire_Designer#Properties_pane|'''Properties''' pane]], set the '''Rules Version''' parameter to '''Latest''', to take advantage of optimized handling of On Change rules during questionnaire loading. To learn more about this parameter, read [[Questionnaire_Designer#Rules_version|Rules version]]. | |||
=== 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 is 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. | |||
=== Sync: download takes too long === | |||
If your app users (inspectors in the field) experience long download times followed by many deletions, consider setting the [[App_projects#Managing_entities|'''Synchronization''' strategy]] for the entity Questionnaire to '''Incremental with Sync Filter'''. | |||
== Tip: Migrating inspections between environments == | |||
If you need to migrate more complex inspections scenarios between environments, for example, for a dev/test environment to production, proceed as follows: | |||
# Migrate the questionnaires (using the [[Questionnaire_Designer#Data_group|export/import function]] of the Questionnaire Designer). | |||
# Migrate the mobile reports (using the [[Report_Designer#Using_the_designer|export/import function]] of the Report Designer) and activate them. | |||
# In Questionnaire Designer, [[Questionnaire_Designer#Actions_group|associate]] the reports to the right questionnaires. | |||
# In Questionnaire Designer, [[Questionnaire_Designer#Configuring_commands|set up the Run Report command]] on each questionnaire to point to the right report template. | |||
# In Questionnaire Designer, activate (non-versioned) or publish (versioned) questionnaire templates. | |||
== Technical information == | == Technical information == | ||