9,291
edits
Inspections: Difference between revisions
Jump to navigation
Jump to search
→Permissions
| Line 130: | Line 130: | ||
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. | ||
== Permissions == | == Technical information == | ||
Resco Inspections utilizes the data-driven architecture rather than the metadata-driven approach. It means that the Resco Inspections data model (entities, fields, relationships) is already created, and when building a new custom questionnaire template you are not altering the data model – instead, you’re adding the entity records. As a consequence, the user who manages the questionnaire templates does not have to be a backend administrator since this user is not changing the data model. | |||
All questionnaire data is saved as records on your backend server (Resco Cloud/Dynamics/Salesforce), in multiple custom entities: | |||
* '''Questionnaire''' (resco_questionnaire) stores information about the questionnaire templates, snippets, and answered questionnaires. Each questionnaire can contain any number of question groups and questions. How is a particular questionnaire record used depends on the following properties: | |||
** As a questionnaire template (if Is_Template = Yes) | |||
** As a snippet (if Is_Snippet = Yes) | |||
** As a filled-in questionnaire | |||
* '''Question Group''' (resco_questiongroup) stores information about the question groups. Each question group can contain multiple questions. | |||
* '''Question''' (resco_question) stores all the questions created for the questionnaire, as well as answers. The unformatted answer value can be found in the Value (resco_value) field; formatted value in the Value Label (resco_valuelabel) field. | |||
* '''Questionnaire Folder''' (resco_questionnairefolder) stores information about the folder structure that organizes questionnaire templates in the designer. Each folder can contain multiple questionnaire templates. Usually, this entity does not need to be enabled in the app project. | |||
When an app user starts a questionnaire in the app, a new copy of the template is created. For an answered questionnaire, we store both questions and answers. This approach ensures that when you change your questionnaire template, existing answered questionnaires are not affected; historical records are not altered. | |||
See also: [https://blog.resco.net/2020/06/02/resco-inpections-for-dynamics-365-data/ Dynamics 365 – how is the data stored?] {{Badge|Blog}} | |||
=== Permissions === | |||
Permissions for Inspections entities need to be set based on what action will the user perform on questionnaires. | Permissions for Inspections entities need to be set based on what action will the user perform on questionnaires. | ||
| Line 149: | Line 169: | ||
It is also possible to manage permissions by assigning ownership of Questionnaires to teams in the backend server. | It is also possible to manage permissions by assigning ownership of Questionnaires to teams in the backend server. | ||
=== Saving questionnaire data === | |||
Questionnaire data can be saved in three different ways: | |||
* Record-based model (default): Each answer in a questionnaire is a record. | |||
* JSON / compressed JSON: Answer are stored in JSON format that might be compressed. JSON requires fewer records and may result in faster synchronization. However, analyzing the answers may require additional effort. | |||
<!-- * Hybrid model (planned for a future release): Combination of the previous two models. For each question, you can configure what you prefer. --> | |||
The data model can be configured on the '''Properties''' pane, in the '''Answer Storage''' field. | |||
=== Completion status === | |||
A questionnaire has a completion status field (resco_completionstatus) that can take three values: | |||
* [0] Active (incomplete, in progress) | |||
* [1] Completed | |||
* [2] Canceled | |||
[[Category:Resco Inspections]] [[Category:Woodford]] [[Category:Resco Mobile CRM]] | [[Category:Resco Inspections]] [[Category:Woodford]] [[Category:Resco Mobile CRM]] | ||