9,309
edits
Releases/Spring 2020: Difference between revisions
Jump to navigation
Jump to search
→Smartwatch integration
| Line 73: | Line 73: | ||
This release brings several small usability updates: | This release brings several small usability updates: | ||
* | * Return to a previously answered questions: It is now possible to go back in the questionnaire on the smartwatch and edit an already answered question.<br>[[File:Spring 2020 smartwatch go back.png]] | ||
* The value entered on the phone shows also on the watch: If there are two people performing an inspection, the data entered on the phone is now displayed also on the watch, so both devices are synchronized in real-time. Until now, it worked only the other way around. | |||
* The phone scrolls down the questionnaire if questions are answered on the smartwatches: As the inspector goes through the questions on the smartwatches, the questionnaire on the phone scrolls down automatically so that the inspector can see the progress through the list of questions and how many questions remain. | |||
=== Augmented reality for tagged image === | |||
The functionality of doing the [[Questionnaire_Designer#Tagged_image|inspections in a holographic 3D scene]] is with the ARKit now available also for the iOS devices. Inspectors can now open the holographic scene on an iPhone/iPad instead of going through the standard questionnaire. Instead of attaching photos to the individual questions or topic groups – inspectors can now go the other way round – to answer the questions directly in the 3D scene and tagging each onto the relevant object. This is done through spatial anchors. The image of the so-called “tagged scene” is then added to the questionnaire and its report. | |||
[[File:Spring 2020 augmented reality.jpg|600px]] | |||
== Platform == | |||
=== New Form Table designer === | |||
On mobile devices, the real estate of the screen is limited and vast empty spaces in apps can feel like a waste. Especially for business users, who’d often prefer to view key information (e.g. contact’s name, address, email, phone, parent account, last visit date & details, etc.) in one place, without the need to scroll extensively. | |||
That’s why we are introducing a new [[Form#Table|Form Table designer]] in Woodford that allows to visually position elements on the screen into highly customized layouts. On form tabs, Resco enables to create tables consisting of various form elements (fields), with up to 20x20 rows and columns. Each row and column’s width can be easily adjusted. Furthermore, each added form element can be flexibly stretched spanning one or multiple cells in one or multiple rows and columns. Ultimately, the new Form Table designer enables admins to easily create layouts that take advantage of any screen size and eliminate extensive scrolling for users to access vital information. | |||
=== Signature flow === | |||
From a young age, we’re all taught not to sign anything until we’ve properly read the entire document. Whether signing an insurance claim assessment or a simple invoice – people like to see what they sign before they put pen to paper. | |||
Up until now, when mobile reports required a digital signature, it needed to be captured before the final PDF has been created. With the Spring Update, in any Resco app, [[Report_Designer_examples#Adding_signatures_to_reports|digital signatures can be added after the report has been finalized]] - a signature pad and (an optional) comment section will be displayed underneath the document. | |||
=== Smooth Power BI integration === | |||
For those utilizing Power BI, Resco has further enhanced its integration with Microsoft’s business intelligence tool. Previously, when accessing Power BI from the Resco app, users needed to enter their Power BI credentials when opening a new iframe displaying Power BI dashboards. From now on, they can access any number of Power BI iframes within one app session without having to enter their login details repeatedly for each. | |||
=== OnChange called for related record events === | |||
A record in the system rarely “lives” on its own. E.g., an account provides only some information and there can be contact, order, task or any other records related to it. These related records can be created, modified, or deleted and these events often need to be reflected on the parent record (account, in our example). | |||
Therefore, in the Spring update, we added the possibility to utilize the OnChange rule when changes occur on related records – so that these changes are immediately reflected on the parent account if required. For example, an account contains information on the total value of its related orders (Total Order Value field). When a new order – related to this account - is created, the OnChange rule will be triggered and the new order’s value will be automatically added to the account’s Total Order Value field. | |||
=== Image actions for Image Detail Items === | |||
Multimedia actions – such as capturing a photo, recording a video, etc. – have been available on a form’s Media tab up until this point. Now, users can also access them directly from the form’s Image Detail item – which makes adding images, videos, or audio even faster. | |||
[[Category:Releases]] | [[Category:Releases]] | ||