Minimizing the number of full page refreshes will maximize the performance of your Webform Server application by reducing bandwidth use and load on the server. Furthermore, it will improve the user experience by reducing reaction times.
A full page refresh requires the form to be sent back to the server, refreshed, and returned to the user. While a single full page refresh may take milliseconds, large form pages, multiple users, or multiple page refresh triggers can considerably slow the process.
However, there are alternatives. Instead of using computes that rely on options that required full page refreshes, design your form so that computes rely on options that support dynamic updates. For example, to highlight a label when the user tabs into a field, you could use a compute either to change the label text to a different color or to change the label text to bold. Changes in font color are updated dynamically, but changes in font style (for example, plain, bold, and so on) require an automatic page refresh. Therefore, a change in font color will happen faster than a change in font style.
You can configure Webform Server to turn off full page refreshes entirely.
The following compute changes the label text to a different color:
<labelfontcolor compute="CHECK1.value == 'on' ? ('blue') : ''"></labelfontcolor>
Exceptions to this practice
There are no exceptions to this practice.