Releases/Fall 2024: Difference between revisions

Revision as of 11:54, 15 August 2024

Releases
Preview release v19.0 Winter 2026 Production releases v18.2 Fall 2025 (latest) v18.1 Spring 2025 v18.0 Winter 2025 v17.2 Fall 2024 v17.1 Spring 2024 v17.0 Winter 2024 v16.1 Fall 2023 v16.0 Spring 2023 v15.3 Winter 2022 v15.2 Autumn 2022 v15.1 Summer 2022 v15.0 Spring 2022 v14.3 Winter 2021 v14.2 Autumn 2021 v14.1 Summer 2021 v14.0 Spring 2021 v13.3 Winter 2020 v13.2 Autumn 2020 v13.1 Summer 2020 v13.0 Spring 2020 v12.3 Winter 2019 v12.2 Autumn 2019 v12.1 Summer 2019 v12.0 Spring 2019 All release notes Security bulletin Deprecations Preview/beta access channel

Warning

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

The 17.2 / Fall 2024 release is planned for September 2024. Find the download links for the latest preview version on the Preview page.

Resco mobile platform (Microsoft, Salesforce, Resco Cloud)

Delete signature after generating report

If you are using enhanced signature flow to sign reports at run time, you can opt to discard signatures as soon as the report is saved. Such signatures remain in the generated reports, but the signature image is removed from the database. When you generate a new version of the report, signature has to be reacquired. This feature can fulfill legal/security requirements, and it can save storage space.

To enable this feature, edit a report with enhanced signature flow enabled in the Report Designer and check Discard signature after report is saved.

Nicer dropdown lists

In the previous release, we have introduced nicer dropdown lists for the iOS version of Resco Mobile CRM. In this release, they are available also for other operating systems.

Support for Aztec codes

Resco Mobile CRM can now read Aztec barcodes. From user perspective, this process is similar to standard barcode scanning.

On iOS, Resco Mobile CRM uses native iOS API.
On Windows, Resco Mobile CRM uses https://github.com/micjahn/ZXing.Net/tree/.
On Android, Resco Mobile CRM uses ML Kit and falls back to ZXing if the ML Kit is not available.

Woodford field usage: more features

In the previous release, we have introduced the feature that identifies fields actively used in the app (so that you can disable the rest and make sync go faster). In this release, we are adding more features, including a whitelist of fields that you don't want to disable.

Theme editor

Node.js upgrade

Node.js in Resco products was updated to version 20.x.

Inspections and questionnaires (Microsoft, Salesforce, Resco Cloud)

Create records from questionnaires

The data mapping feature of questionnaires now allows you to create new records from questionnaires.

Questionnaire Designer: collapsible side panes

In the Questionnaire Designer, you can hide the left and right panes. This leaves more space to focus on the questionnaire body.

Questionnaire Designer: fields adapt to content

When editing questions in the designer, various fields automatically adapt and grow when you enter longer text.

Questionnaire Designer: shorter question names

When a user creates a new question, its name is automatically derived from the question label. If the label is very long, the name can get long, too. This affects the final size of questionnaire negatively. Questionnaire Designer now takes a maximum of 15 characters from the question label and adds a unique suffix if needed.

Locate mandatory questions

When answering a questionnaire in Resco Mobile CRM, when you save or complete the questionnaire and the validation fails, the focus is automatically moved to the first mandatory question that needs attention. All other questions that need answers are marked with an alert icon in the question header.

Data mapping order

Before this change, the mappings were applied when loading the questionnaire, but as the values of lookups were just references, the chained mappings (fields that have that lookup as a source of its mappings) were not able to fill in the mapped values.

We now detect the order of bindings and apply mappings sequentially, so that even mappings like "Regarding->LookupA->LookupB->TextC" fill all the data properly.

Warning

Breaking change: The smart defaults are now loaded prior to applying the mappings. When the smart default value is set to the lookup, fields that have this lookup as a source will now have the data from that default value.

Resco modules for Power Platform and Dataverse (Microsoft)

JavaScript support in questionnaires on Power Platform

Questionnaire Player on model-driven apps and Power Pages now supports JavaScript. You can enhance the questionnaires with your own custom logic.

openQuestionnaireWithTemplateName

The Questionnaire Player controller on Power Pages now supports a new method, openQuestionnaireWithTemplateName. Use the method if you want to identify the questionnaire by template name. Optionally, include the version number, or use the latest version by default. See the full list of methods for reference.

Simpler Forms+ setup

Getting starting with Resco Forms+ has been simplified. We have created a default fallback Woodford project so that new users of Forms+ don't have to create one (and possibly never touch Woodford again).

@@ Line 1: / Line 1: @@
 {{Releases TOC}} {{WIP}}
 The 17.2 / Fall 2024 release is {{Popup|planned|The apps are released first (gradual rollout). The server part follows within a few days.}} for '''September 2024'''. Find the '''download''' links for the latest preview version on the '''[[Preview#Where_to_find_beta_releases|Preview page]]'''.
+== Resco mobile platform (Microsoft, Salesforce, Resco Cloud) ==
+=== Delete signature after generating report ===
+If you are using enhanced signature flow to [[Report_Designer_examples#Signing_reports_at_run_time|sign reports at run time]], you can opt to discard signatures as soon as the report is saved. Such signatures remain in the generated reports, but the signature image is removed from the database. When you generate a new version of the report, signature has to be reacquired. This feature can fulfill legal/security requirements, and it can save storage space.
+To enable this feature, edit a report with enhanced signature flow enabled in the [[Report Designer]] and check '''Discard signature after report is saved'''.
+[[File:Discard-signature-after-use.png|alt=discard-signature-after-use]]
+=== Nicer dropdown lists ===
+In the previous release, we have introduced [[Releases/Spring_2024#(iOS)_nicer_dropdown_lists|nicer dropdown lists for the iOS]] version of Resco Mobile CRM. In this release, they are available also for other operating systems.
+=== Support for Aztec codes ===
+Resco Mobile CRM can now read [https://en.wikipedia.org/wiki/Aztec_Code Aztec barcodes]. From user perspective, this process is similar to standard [[barcode scanning]].
+* On iOS, Resco Mobile CRM uses [https://developer.apple.com/documentation/avfoundation/avmetadataobjecttype?language=objc native iOS API].
+* On Windows, Resco Mobile CRM uses https://github.com/micjahn/ZXing.Net/tree/.
+* On Android, Resco Mobile CRM uses [https://developers.google.com/ml-kit/vision/barcode-scanning ML Kit] and falls back to ZXing if the ML Kit is not available.
+=== Woodford field usage: more features ===
+In the previous release, we have [[Releases/Spring_2024#Woodford:_find_fields_used_in_the_mobile_app|introduced the feature]] that identifies fields actively used in the app (so that you can disable the rest and make sync go faster). In this release, we are adding more features, including a whitelist of fields that you don't want to disable.
+[[File:Check-field-usage-fall-2024.png|600px|alt=check field usage screen as modified in fall 2024 release]]
+[[File:Check-field-usage-whitelist.png|600px|alt=manage a whitelist of fields that should not be disabled even if unused]]
+=== Theme editor ===
 === Node.js upgrade ===
@@ Line 6: / Line 38: @@
 Node.js in Resco products was updated to version 20.x.
-=== openQuestionnaireWithTemplateName ===
+== Inspections and questionnaires (Microsoft, Salesforce, Resco Cloud) ==
-The Questionnaire Player controller on Power Pages now supports a new method, openQuestionnaireWithTemplateName. Use the method if you want to identify the questionnaire by template name. Optionally, include the version number, or use the latest version by default. See [[Inspections_on_Power_Platform#List_of_methods|the full list of methods]] for reference.
 === Create records from questionnaires ===
@@ Line 14: / Line 44: @@
 The [[data mapping]] feature of questionnaires now allows you to create new records from questionnaires.
-=== Collapsible side panes in Questionnaire Designer ===
+=== Questionnaire Designer: collapsible side panes  ===
 In the Questionnaire Designer, you can hide the left and right panes. This leaves more space to focus on the questionnaire body.
@@ Line 43: / Line 73: @@
 {{Note|Breaking change: The smart defaults are now loaded prior to applying the mappings. When the smart default value is set to the lookup, fields that have this lookup as a source will now have the data from that default value.|Warning}}
+== Resco modules for Power Platform and Dataverse (Microsoft) ==
 === JavaScript support in questionnaires on Power Platform ===
@@ Line 48: / Line 80: @@
 Questionnaire Player on model-driven apps and Power Pages now supports JavaScript. You can enhance the questionnaires with your own custom logic.
-=== Delete signature after generating report ===
+=== openQuestionnaireWithTemplateName ===
-If you are using enhanced signature flow to [[Report_Designer_examples#Signing_reports_at_run_time|sign reports at run time]], you can opt to discard signatures as soon as the report is saved. Such signatures remain in the generated reports, but the signature image is removed from the database. When you generate a new version of the report, signature has to be reacquired. This feature can fulfill legal/security requirements, and it can save storage space.
+The Questionnaire Player controller on Power Pages now supports a new method, openQuestionnaireWithTemplateName. Use the method if you want to identify the questionnaire by template name. Optionally, include the version number, or use the latest version by default. See [[Inspections_on_Power_Platform#List_of_methods|the full list of methods]] for reference.
-To enable this feature, edit a report with enhanced signature flow enabled in the [[Report Designer]] and check '''Discard signature after report is saved'''.
-[[File:Discard-signature-after-use.png|alt=discard-signature-after-use]]
-=== Nicer dropdown lists ===
-In the previous release, we have introduced [[Releases/Spring_2024#(iOS)_nicer_dropdown_lists|nicer dropdown lists for the iOS]] version of Resco Mobile CRM. In this release, they are available also for other operating systems.
-=== Support for Aztec codes ===
-Resco Mobile CRM can now read [https://en.wikipedia.org/wiki/Aztec_Code Aztec barcodes]. From user perspective, this process is similar to standard [[barcode scanning]].
-* On iOS, Resco Mobile CRM uses [https://developer.apple.com/documentation/avfoundation/avmetadataobjecttype?language=objc native iOS API].
-* On Windows, Resco Mobile CRM uses https://github.com/micjahn/ZXing.Net/tree/.
-* On Android, Resco Mobile CRM uses [https://developers.google.com/ml-kit/vision/barcode-scanning ML Kit] and falls back to ZXing if the ML Kit is not available.
-=== Woodford field usage: more features ===
-In the previous release, we have [[Releases/Spring_2024#Woodford:_find_fields_used_in_the_mobile_app|introduced the feature]] that identifies fields actively used in the app (so that you can disable the rest and make sync go faster). In this release, we are adding more features, including a whitelist of fields that you don't want to disable.
-[[File:Check-field-usage-fall-2024.png|600px|alt=check field usage screen as modified in fall 2024 release]]
-[[File:Check-field-usage-whitelist.png|600px|alt=manage a whitelist of fields that should not be disabled even if unused]]
-=== Theme editor ===
 === Simpler Forms+ setup ===
 Getting starting with [[Resco Forms+]] has been simplified. We have created a default fallback Woodford project so that new users of Forms+ don't have to create one (and possibly never touch Woodford again).