Test Page

Roadmap highlights and priorities

Components library

An organization has multiple questionnaires (usually), and most of the time they share sections. Components library allows quick reuse and management of these sections consisting of questions, groups of questions and corresponding logic.

Data Layer

Data driven architecture of Questionnaires allows great flexibility without the need to create metadata on the backend system. To be effective, it requires optimized data storage (e.g. whole Questionnaire as JSON) and synchronization.


The information collected by the field teams can be viewed and evaluated in web-based tools to provide statistics and insights for individual answers as well as whole questionnaires and show custom reports with configurable dashboards and charts based on collected data.

All features and details



In an environment where an organization operates in multiple countries or in a country with multiple official languages it is usually required to manage the same questionnaire, but in different languages. This means having the same questions and the same logic, but the texts – question labels, descriptions and answers options, etc. in multiple language variations.
Our goal is to provide support for this in an easy to access way, directly in the Questionnaire Designer, so different text versions can be provided there. Also, export/import function should be available for efficient translate options.


Components library – Snippets

The simplest form of a component is a ‘Snippet’ – element reusable in different Questionnaires. A snippet can be a question, a question group or multiple question groups. It can be created by selecting elements in an existing questionnaire (or creating a new one from scratch) and copying them into the Snippets library. Corresponding rules will be copied into the library as well, but their editing is only possible in Snippets library editor.
Once a snippet is created, it can be pasted into any questionnaire, possibly also multiple times to reduce manual re-creation of the same functionality repeatedly. Once pasted, it becomes part of the Questionnaire and loses any connection to original Snippet, so further changes to a Snippet in the library are not reflected in Snippets already pasted in existing Questionnaires.


Components library – Composite components

Snippets streamline the process of reusing portions of a Questionnaire, but they lose connection to the original Snippet the moment they are pasted. This means that making a change into all occurrences of a Snippet pasted into multiple Questionnaires is not possible.
Composite components resolve this issue. They remain the connection to the original component, so all future updates to the component are reflected in all Questionnaires, where this component is used. A composite component is a ‘black box’ which has inputs and outputs. Once inserted into a Questionnaire it remains non-modifiable, so future changes to the component are possible only in component library.


Pages and decision tree

Many Questionnaires are structured as process dialogs or wizards – they take inspector step by step through the process, with each step displaying one or more questions and each answer possibly changing the next step in the process.
In Resco Inspections, we will model this approach with Pages. At any given moment in time, only one page is displayed. Each Page can display one or more questions and question groups. Based on precisely defined decision tree a set of answers on one page might lead to a certain page being displayed as next, or a completely different one.
The decision tree driving the process is a key element and will be displayed in specific interface allowing visual representation and editing, so the relationships between pages are immediately apparent.


Data Layer improvements

Data driven architecture of Questionnaires allows great flexibility without the need to create metadata on the backend system. However, representing each question and answer as a record is sometimes not effective, and therefore we will introduce following options –

  • Optimized Storage – Instead of storing each answer as a record, we will store all answers to a certain Questionnaire in one record as JSON object. This will streamline the synchronization process and data storage however it will make it more difficult to integrate with other tools (e.g. reporting).
  • Hybrid Storage – Similarly to Optimized Storage Hybrid Storage will store answers to a Questionnaire as JSON object, but only for selected questions. Remaining questions/answers will be stored as records, so they can be easily used with other reporting tools.
  • Mapping – Instead of using Resco entities, the result of a Questionnaire can be stored in a separate entity / object. Any standard or custom entity / object can be used, with mapping from question to field providing the projection from questionnaire to a record.


More question types

Different organizations have different requirements and to capture all the different types of data these organizations need, we’ll provide additional question types such as –

  • Rating (1..N stars) to be able to rate a product or a service in a visual way
  • Table to be able to select multiple options from a database table (e.g. select products customer is interested in)


Automatic Dashboard

Data collected using Resco Inspections can be analyzed using the standard analytics tools available in the respective backend, but for immediate and quick analysis Resco provides Automatic Dashboard. For each Questionnaire Template, this dashboard offers an overview for completed Questionnaires and collected data – for each question a corresponding representation is selected (a chart, a list …) displaying the ranges and values of answers. Without any additional setup, Automatic Dashboard allows direct insight into inspection process, where filtering on the user, dates and additional criteria allows for effective drill down into data.



The process of designing a Questionnaire can result in complex inspection questionnaires, with multiple different paths and convoluted logic behind the process. The ability to immediately test the designed Questionnaire as a preview – as the user would see it in the mobile application – will make this process significantly more effective. The preview will be part of the browser experience, directly launched from Questionnaire Designer.



Resco Inspections can utilize existing business data by connecting to external data sources. The setup for these sources can be simplified, focusing on different aspect of the setup and demo experience –

  • Install demo questionnaires
  • Add Questionnaire views (Answered, Templates, cells)
  • Create metadata connection between Questionnaires and entity (e.g. appointment, M:N entity)
  • Add Questionnaire as associated tab to entity
  • Add Questionnaires to home
  • Add a Questionnaire Form / Viewer to the browser app (Dynamics 365 / Salesforce)

Last updated: 27.2.2019


The work on this feature has already started. The expected delivery date in next release (usually March, June, September or December), but if the feature is more complex it might require two release cycles to be completed.


The feature has been implemented and will be released in Resco’s forthcoming release (next: June 2019).


This feature is on Resco’s roadmap and is waiting to be picked up by the development pipeline to get implemented.


The feature has been released in last Resco’s release (Version 12.0 – March 2019).

Please note Resco’s Roadmap might be subject to change. The outlined features may be modified or updated before commercial release. Resco makes no warranties with respect to the information provided.