9,291
edits
Form: Difference between revisions
Jump to navigation
Jump to search
→Caching forms
| Line 134: | Line 134: | ||
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: | ||
* Project Default: | * Project Default: Respect the global form caching policy. | ||
* Disable Caching: | * Disable Caching: Disable caching for a particular type of the form - the app always creates a new instance of this form. | ||
* Force Caching: | * Force Caching: Enforce 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. | ||
{{Note|As general rule, disabling caching is a good solution when you have many visibility rules and your form doesn’t contain many | {{Note|As a general rule, disabling caching is a good solution when you have many visibility rules and your form doesn’t contain many iframes or other types of tabs requiring complex initialization. Another use case is when you don’t expect users to browse through many records in quick succession, e.g., looking for the right order by checking order details by going through the orders list.}} | ||
== What form is used? == | == What form is used? == | ||