Releases/Winter 2024

Warning

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

The 17.0 / Winter 2024 release (name pending) is planned for January 2024.

Resco mobile platform (Microsoft, Salesforce, Resco Cloud)

Salesforce QoL improvements

No need to reconnect organization after sandbox refresh or organization changed

Until this release, Salesforce admins had to go through tedious process of reconnecting Resco with Salesforce whenever organization name or ID changed. Admin had to backup all Resco related data such as App Projects or Mobile Reports. This procedure was especially daunting after full-refresh of Sandbox. Now it is no longer needed. The only reason an admin needs to reconnect is when url of organization changes.

Faster metadata update

We are listening to feedback regarding long metadata update times and in this release we made sure it is way faster than before. Expect even more optimizations in the upcoming previews.

Bring some color to flexible forms

As you probably know, forms in the mobile apps can be displayed in two ways:

• Tabbed view: one tab at a time + tab selector at the top or bottom
• Flexible view: all form content displayed at once, available by scrolling if it does not fit on the screen

This release brings more control over how flexible forms are displayed. First of all, we're introducing the industry-standard term cards. This is what we call the individual blocks on flexible forms. Previously, we used to call them tabs - but flexible forms have no tabs.

More importantly, you can now define a custom color scheme for cards. Colors allow users to easily distinguish where cards start and end. This is important because cards group related information into a single block - less chance for confusion among the users.

So how to get started? Edit the theme in Woodford and enable Advanced color settings. Note the new set of colors in the Card section. So go ahead an make your cards stand out.

Inspections and questionnaires (Microsoft, Salesforce, Resco Cloud)

OCR

A regular maintenance visit, for example, inspecting a piece of machinery, can be often smooth if your questionnaire is well designed and guides users through all the necessary steps. The process of registering a new piece of machinery into the database can be much more complicated and prone to errors. If the inspector has to read some details about a piece of machinery and enter them into the app... OCR comes to the rescue. Users can take a photo of the product label, let the device extract text from the image, and use the text as answers.

1. Edit a questionnaire template.
2. Go to Options and set Feature version to "3 - Latest".
3. Select a question of the type "Text" or "Multiple Lines of Text".
4. On the Properties pane, select Enable OCR.
5. As OCR reference image, do one of the following:
   • Select one of the existing images from the questionnaire template. The image answer will be used as OCR source. This must be a single-image answer (Max Count=1).
   • Leave the field empty. Users can create or choose an image as usually, but the image won't be saved as part of the questionnaire.
6. Save all changes.

In the app, OCR is available for Windows Android, iOS, and Windows UWP edition of the app; both offline and online. The exact function and performance depends on the capability of the device's native OCR library. As usually, large and high-resolution images may take a while to process. Resco cannot guarantee the quality and/or performance of the OCR library.

The app displays the image with extracted text superimposed on it. Users can select which line of text from the image they want to save into a particular text field. They can edit the extracted phrase before storing it as the answer.

(November preview) Import wizard

The process for importing questionnaire templates has been redesigned to support different scenarios. Users have more control over what and how to import.

Resco Cloud platform

{{#CI form: title = Was this information helpful? How can we improve? | type = inputs | [textarea] }}