10,887
edits
Salesforce admins: Urgent action required!
Releases/Fall 2023: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 2: | Line 2: | ||
The 16.1 / Summer 2023 release (name pending) is planned for '''September 2023'''. The first [[beta|public preview]] is now available. | The 16.1 / Summer 2023 release (name pending) is planned for '''September 2023'''. The first [[beta|public preview]] is now available. | ||
== | == Resco mobile platform (Microsoft, Salesforce, Resco Cloud) == | ||
=== | === Reports saved in file columns === | ||
It is now possible to [[configure Run Report command]] to store the generated document in file columns belonging to the source report entity. The columns can be selected in the '''Save report to entity''' field. | |||
[[File:Configure run report command - save to file column.png|600px]] | |||
; Prerequisites: | |||
* Both the File Column and its Filename fields must be enabled in Woodford. | |||
* The parent entity form must contain file column. | |||
;Notes: | |||
* | * Saving the document in the report dialog will only store it in a file column field of the parent form. The report is saved with the parent form. This applies even when '''Immediate Action''' is set to "SaveAndClose". | ||
;Limitations: | |||
* Only supported in Online mode. This is a temporary limitation until synchronization of File Columns is available. Offline support is planned for general availability in 16.1 (September 2023), preview is planned for the end of June. | |||
* Digital signature flow (DocuSign) via eSignature command is not supported with File Columns. | |||
* Only applicable for Run Report Command on entity forms. Storing reports from on Views and Questionnaires is not supported. | |||
=== | === SyncStats analyzer === | ||
[[ | [[SyncStats analyzer]] is a tool that analyzes multiple sync logs and extracts 30+ different indicators to identify the most frequent problems and characterize average sync performance. | ||
= | === Dataverse/Dynamics: Better file columns support === | ||
== Dataverse/Dynamics | |||
Users can now create, modify, or delete the contents of [[file column]]s on entity forms in [[Resco mobile apps]]. | Users can now create, modify, or delete the contents of [[file column]]s on entity forms in [[Resco mobile apps]]. | ||
| Line 68: | Line 45: | ||
* Images can be stored in File columns, but it is not possible to use Image Editor to change them. It is still possible to resize them, though. | * Images can be stored in File columns, but it is not possible to use Image Editor to change them. It is still possible to resize them, though. | ||
== Inspections == | === Resco Mobile CRM: end of life for older iOS versions === | ||
Resco Mobile CRM now requires iOS 12 or later. As a result, iPhones 5 and 5c are no longer supported. (Before this release, Resco mobile apps used to support iOS 10+) | |||
== Resco modules for Power Platform and Dataverse (Microsoft) == | |||
=== Inspections in Power Pages === | |||
Originally, Resco questionnaires were designed to be displayed and answered in [[Resco mobile apps]]. Later, we introduced the option to place a "[[Questionnaire Player]]" to a form of your Dynamics/Dataverse table, allowing you to display/answer questionnaires on Dynamics/Dataverse web. With this release, you can place the Questionnaire Player on a Power Page. | |||
This feature is available on-demand as an '''early alpha'''. Contact us using TBD if you want to experiment with it. Or you can wait for a beta version planned for later this year. | |||
=== Guides in Power Apps === | |||
Guides are now fully supported on Dataverse/Dynamics without Woodford. | |||
* Install the latest guides solution package. | |||
* Instead of Woodford, administration settings are configured in the environmental settings of the Power Apps solution. The settings with the "rh_" prefix apply to guides. | |||
: [[File:Make powerapps guide admin settings.png|600px]] | |||
* Instead of Resco mobile apps, you can display guides in Power Apps. The guides solution package comes with default views and a form for the Guide table. For example, you can add a list of related guides to your assets. | |||
: In the example below, guides were added to the Idea table. The guide form displays the content of the guide. | |||
: [[File:Guides in power apps 1.png|600px]] [[File:Guides in power apps 2.png|600px]] | |||
== Inspections and questionnaires (Microsoft, Salesforce, Resco Cloud) == | |||
=== Rename [Clear] option in option set === | === Rename [Clear] option in option set === | ||
| Line 85: | Line 84: | ||
Alternatively, you can edit the questionnaire template in the [[Questionnaire Designer]] and lower the feature version to ensure that the questionnaire stays compatible with older app versions. However, some newer questionnaire features will be unavailable. If you're familiar with Woodford projects, this is similar to [[Publishing_app_projects#Publishing_with_older_version|publishing app projects with older Publish Version]]. | Alternatively, you can edit the questionnaire template in the [[Questionnaire Designer]] and lower the feature version to ensure that the questionnaire stays compatible with older app versions. However, some newer questionnaire features will be unavailable. If you're familiar with Woodford projects, this is similar to [[Publishing_app_projects#Publishing_with_older_version|publishing app projects with older Publish Version]]. | ||
== Guides == | == Resco Guides (Microsoft, Resco Cloud) == | ||
=== Full-text search === | === Full-text search === | ||
| Line 92: | Line 91: | ||
[[File:Search in guides.png|600px]] | [[File:Search in guides.png|600px]] | ||
<!-- === Localization === | <!-- === Localization === | ||
| Line 106: | Line 104: | ||
[[File:Localizing guides.png|600px]] | [[File:Localizing guides.png|600px]] | ||
--> | --> | ||
== Resco Cloud platform == | |||
=== Azure Table for storing server audit data === | |||
[[Resco Cloud]] server audit data can now be stored in [[Auditing#Enable_collection_of_audit_data_in_Resco_Cloud|Azure Table]]. | |||
=== Calculated fields === | |||
Resco is traditionally strong with client-side [[business logic]]: no-code rules and JavaScript support help you fine-tune the behavior of your mobile app. However, in many scenarios, server-side logic is preferable. '''[[Calculated fields]]''' help to fill that niche. These fields '''derive their value from other fields'''. | |||
* Use the [[Admin Console]] to define the fields. Set up the formula for calculating the value. | |||
* Server automatically updates the fields when the fields used in the formula change. | |||
* Calculated fields can be displayed in [[Resco mobile apps]], but they should be read-only. | |||
=== Rise of the clones === | |||
When using [[Admin_Console#Environments|connected environments]] to create a clone organization, you can now enter a custom name of the new organization. Perhaps more importantly, you can optionally include what cloud environment to use. For example, you can clone your production organization to the [[beta|preview/beta]] cloud. | |||
<pre> | |||
https://{custom org name}.app.resco.net - production | |||
https://beta.rescocrm.com/{custom org name} - preview/beta channel | |||
</pre> | |||
=== Label position BorderTop is now supported in web app === | |||
Resco web app (i.e., Resco Mobile CRM running in a web browser) now supports label position set to BorderTop. | |||