Releases/Spring 2024

From Resco's Wiki
Jump to navigation Jump to search
Releases
Preview release

Production releases

Warning Work in progress! We are in the process of updating the information on this page. Subject to change.

The 17.1 / Spring 2024 release is planned for May 2024. Find the download links for the latest preview version on the Preview page.

Resco mobile platform (Microsoft, Salesforce, Resco Cloud)

Geofencing

The geofencing feature of Resco mobile apps (Android, iOS) introduced in release 17.1 allows you to get immediate updates when your front-line workers enter or leave one of your predefined locations (such as office, service location, etc.). This works reliably on a wide range of devices with minimal battery impact and improved user privacy (only presence at pre-set locations is monitored, not the overall location)​.

JSBridge upgrade for web app

In order to improve security, browser compatibility, and performance of Resco JavaScript Bridge on web app, we strongly recommend to upgrade your JSBridge.js to the latest version. However, you need to do it after the release of 17.1. You don't have to update your code.

Resco web app allows you to access your app projects from a web browser. Web app is available for Resco Cloud server; however, there's also a hidden WebApp web resource in Resco Suite (Dataverse, Dynamics, Power Platform).

This change does not affect Resco mobile apps in any way.

Microsoft Store app: switch to WebView2

We are deprecating legacy WebView in Microsoft Store app. To avoid warnings in Woodford and in the app, go to project Configuration and Use Edge WebView2.

OCR in forms

You can now use OCR to populate text fields on forms. Take a photo or open any picture, let the device recognize the text on the image, and then select portions of the text to populate fields on the form.

Too much flexibility in forms

When defining the layout of flexible forms in Woodford, you can place cards into left panel or right panel. However, the app does not strictly follow this arrangement; sometimes, cards shift around to make the panels equally high. With this release, you can disable this screen real estate optimization: set Cards Layout to "Strict" on the form layout page.

strict cards layout in flexible forms

View designer redesigned

We have modernized the Woodford user interface for designing and configuring views. You can immediately see all rows included in a view. The properties have been revised.

modern view designer

View designer: responsive resize

We have changed how field cells behave in views. Cells set to Responsive Resize grow wider when the available space for the entire view row increases. Empty spaces between cells don't change width. If you disable responsive resizing, you can Anchor the left or right border of the cell.

define cell flexibility in views

View designer: custom map pin

We have changed how you can configure custom map pins in the view designer.

To define a custom map pin binding, click Add Map Pin. A new "Configure Map Pin" window opens.

custom map pin dialog

When you add a custom map pin to the row, it's displayed above it.

custom map pin on the view

Woodford: find fields used in the mobile app

When designing an app project in Woodford, an important paradigm is reducing the amount of server data that gets synchronized on the mobile device:

  • Select only the necessary entities.
  • Select only the necessary fields.
  • Select only the necessary records.

In this release, we're introducing a useful tool for the project designers, helping them answer the question: Which fields are actually in use? Can we turn them off?

Woodford: more clarity into "Project Default"

In Woodford, when editing an app project, you can set the project default values in the Configuration. Later, for example when designing views, one can see that a particular property is set to "Project Default". Previously, Woodford admins had to go to Configuration and check what was the default setting. With this release, in many locations across Woodford, particularly in the view and form designers, they can immediately see the default value in parentheses.

Properties-with-default-in-parentheses.png

Max Columns was changed to just "Default (2)" since the default value does not come from Configuration, but is hardcoded in Resco mobile apps.

Newly supported FetchXML operators

Resco Mobile CRM now supports the following additional FetchXML operators:

  • neq
  • begins-with, not-begin-with
  • ends-with, not-end-with

RFID scanning

Resco mobile apps can connect to Zebra Technologies' RFD4031 RFID scanner using Bluetooth. When the user scans RFIDs, the app can handle this event using JSBridge. The list of all nearby RFID tags is available for further processing.

This feature is available for iOS only.

Dataverse performance improvements

We have sped up the download of metadata from Dataverse. Several metadata-heavy actions should be faster.

Housekeeping: .NET 8

Resco mobile apps (Android, iOS) and other internal components now use .NET 8 instead of .NET 7 which is reaching its end of life in May 2024.

Resco modules for Power Platform and Dataverse (Microsoft)

Better support of images

Working with images in questionnaires is easier in the Power Apps.

  • tagged image
  • image gallery

QR codes in PowerApps

When using Resco questionnaires in the Microsoft Power Apps app, you can now scan QR codes to answer questions.


Inspections and questionnaires (Microsoft, Salesforce, Resco Cloud)

Mark mandatory questions

When answering questionnaires, mandatory questions are now marked with an asterisk.

Required questions are marked with an asterisk.

Support for zero instances for repeatable group

Questionnaire templates now support zero instances of a repeatable group. In the Questionnaire Designer, you can set the Min Repeat Count property down to 0. When filling questionnaires, you can remove also the first instance of a repeatable group if you don't need it. Only the header row is displayed, with a plus button for creating the first instance of the group.

Define score ranges for group results

You can now set question group results for each group. Define group score ranges and assign distinct labels for each range.

  1. Edit a questionnaire template in the designer.
  2. Enable scoring in questionnaire options.
  3. Select a question group.
  4. In the Properties pane, enable Customize Results.
  5. At the end of the group, set up Question group results: Define score ranges and assign labels.

Save answers to different table (not yet available for preview)

Traditionally, questionnaire templates and answers were saved in the same table (entity): resco_questionnaire. With this release, you can select a dedicated table for storing answered questionnaires: resco_questionnaireanswer. This division is particularly beneficial for large installations. Sync filter can be better optimized, resulting in faster sync times. Different tables for templates and answers also allow for more granular security and access control.

Select the table where to store questionnaire answers

Questionnaire integrity check

Rarely, as a result of interrupted sync or gross misconfiguration, it can happen that a downloaded questionnaire does not have all the necessary dependent records (questions, groups, annotations). With this release, the questionnaire player in Resco mobile apps and the web app now checks questionnaire integrity before attempting to display it. This ensures that any missing parts are handled gracefully.

Resco Guides (Microsoft, Resco Cloud)

Guides for Salesforce

In this release, we are debuting Resco Guides for Salesforce users.

Resco Cloud