10,898
edits
(Created page with "{{Releases TOC}} {{WIP}} The 16.1 / Summer 2023 release (name pending) is planned for '''September 2023'''.") |
No edit summary |
||
Line 1: | Line 1: | ||
{{Releases TOC}} {{WIP}} | {{Releases TOC}} {{WIP}} | ||
The 16.1 / Summer 2023 release (name pending) is planned for '''September 2023'''. | The 16.1 / Summer 2023 release (name pending) is planned for '''September 2023'''. | ||
== Resco Cloud == | |||
=== 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. | |||
== 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. |