10,730
edits
Line 122: | Line 122: | ||
To create a new simple form, proceed as follows: | To create a new simple form, proceed as follows: | ||
# Select an entity in the '''Project''' menu and click '''Show UI'''. | # Select an entity in the '''Project''' menu and click '''Show UI'''. | ||
# Click '''New Form''' and name it, then click '''OK'''. | # Click '''New Form''' and name it, then click '''OK'''.<br>(Change the '''Template''' from the default "Standard Form" only if you're setting up the [[bulk update]] command. See below for information about the '''Cache Mode'''.) | ||
# Use the form designer to customize your form: add more fields, add more tabs, add additional objects. | # Use the form designer to customize your form: add more fields, add more tabs, add additional objects. | ||
# Click '''Save & Close''' to save your changes. | # Click '''Save & Close''' to save your changes. | ||
=== 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. | |||
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: | |||
* Project Default: Respects the global form caching policy. | |||
* Disable Caching: Disables caching for a particular type of the form - the app always creates a new instance of this form. | |||
* Force Caching: Enforces caching for a particular type of the form - the app always keeps this type of form in cache and reuses it when opening another entity record. | |||
== What form is used? == | == What form is used? == |