10,730
edits
Important: Deprecating old WebView — Publish failed error
Releases/Winter 2020: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(release preview is up) |
No edit summary |
||
| Line 4: | Line 4: | ||
* [https://blog.resco.net/2020/11/11/resco-winter-update-preview-whats-cooking-for-partners Release preview] {{Badge|Blog}} | * [https://blog.resco.net/2020/11/11/resco-winter-update-preview-whats-cooking-for-partners Release preview] {{Badge|Blog}} | ||
== Inspections == | |||
== Innovations == | |||
-- | === Houston on Android === | ||
Houston is now on iOS, Android, and web apps. Although the augmented-reality (AR) capabilities are not available yet on Android, if a call is initiated from an AR-enabled iOS device, the caller with an Android device can do the drawings and provide remote visual guidance to the iOS colleague. The full AR integration and plane detection is planned for Q1. | |||
Another good news is that Android support makes Houston available also on ruggedized devices such as Cat S61, [[Zebra]], or RealWear HMT1. | |||
[[File:Ruggedized.jpg]] | |||
=== Houston on any form === | |||
With the latest release, users no longer need an [[Mobile_users#Types_of_license|Inspections license]] to use Houston. Consequently, they can access Houston calls from a standard entity [[form]]. There is one difference between Houston on questionnaires and forms: | |||
* On questionnaires, the Houston (or Remote Assistance) button is added automatically to the hamburger menu. | |||
* On forms, you need to add this command manually for each entity. | |||
==== Adding Houston to forms ==== | |||
# Edit the app project. | |||
# Select the entity from the '''Project''' menu. | |||
# Click '''Show UI''' to display the list of views, forms, and charts. | |||
# Double-click the [[Form#Add_commands|form]] where you want to add the Houston command. | |||
# Click '''Edit''' to display the [[command editor]]. | |||
# Add '''RemoteAssistance''' to the '''Selected Commands''' pane. | |||
# Save everything and publish the project. | |||
[[File:Adding houston to entity form.png|600px]] | |||
=== Houston: calling from the web === | |||
Another functionality that was added is the ability to initiate Houston calls from the web app (until now you were able to only accept calls on the web). The process is the same as for a mobile app – open any questionnaire or a standard entity form and select the appropriate command from the hamburger menu. After the call is initiated, the caller operates within the standard web interface. | |||
[[File:Houston call web app.jpg]] | |||
=== Houston: plane detection === | |||
By implementing plane detection, the precision of the drawing got to another level. The AR annotations now stick to the object even when the device is moving. | |||
The following example shows how in reality the “planes” or the surfaces are read by an iPad LIDAR Pro. | |||
[[File:Houston plane detection.jpg]] | |||
Houston video: https://www.youtube.com/watch?v=Byvxcuq9K1w {{Badge|Webinar|YouTube}} | |||
== Platform == | |||
=== Beautified default templates === | |||
Resco set its foot to making the app more visually appealing – starting with some default templates. With the implementation of Sections into the [[home screen|Home form menu]], you can also see new icons and default templates organization. Here is a list of the templates that were reworked: | |||
* Resco Cloud – Sales | |||
* MS Dynamics – Default | |||
* MS Dynamics – Inspector | |||
* MS Dynamics – Schedule Manager (?) | |||
=== Resco on RealWear === | |||
RealWear is a ruggedized head-mounted tablet (HMT1) that is suitable for rough environments. It can operate in rain, dust, freezing, or very noisy environments. With the aim of covering as many use cases and scenarios as possible, you can now use simpler workflows (including Houston) on RealWear devices. It is fully voice-operated and Resco is one of the few (if not the only) providers of both digital workflows and remote calls. A yet more comprehensive set of features is planned for the next release. | |||
=== Synchronization: potential performance saver === | |||
Advanced sync setup (using the sync config file) now offers an additional option, primarily for Dynamics users. | |||
You can now configure incremental sync to not sort records by the versionnumber field. Microsoft recommends using versionnumber sorting as it greatly improves the performance of some fetches. However, our tests show that in some cases, it has the opposite effect. Setting on/off this flag can change fetch performance from minutes to a fraction of a second - or vice versa. The reason apparently lies in the SQL server setup (definition of indexes, etc.) and cannot be predicted. Use this flag as the last resort if you have an extremely slow fetch in incremental sync. See [[Advanced_sync_setup#Disabled_sorting_by_version_number|Disabled sorting by version number]] for more information. | |||