10,730
edits
Important: Deprecating old WebView — Publish failed error
Form: Difference between revisions
Jump to navigation
Jump to search
→Caching forms
| Line 128: | Line 128: | ||
=== Caching forms === | === Caching forms === | ||
Form caching is a practice in Resco mobile apps that once a form is drawn, for example, to display the details of a particular account record, switching to a different record is fast. Only the data is replaced; tabs that were collapsed stay collapsed, fields that were hidden remain hidden, etc. | Form caching is a practice in [[Resco mobile apps]] that once a form is drawn, for example, to display the details of a particular account record, switching to a different record is fast. Only the data is replaced; tabs that were collapsed stay collapsed, fields that were hidden remain hidden, etc. | ||
The benefits of caching are clear: working with the app is much faster. Problems may occur if you're using (poorly written) business logic that relies on the form being in the initial default state. You can set up form caching on project level in the project [[Configuration#Forms|Configuration]], or you can override this in form properties. The following options are available: | The benefits of caching are clear: working with the app is much faster. Problems may occur if you're using (poorly written) business logic that relies on the form being in the initial default state. You can set up form caching on project level in the project [[Configuration#Forms|Configuration]], or you can override this in form properties. The following options are available: | ||