You can reduce a form’s load and run time by minimizing the frequency in which you use itemlocation
When designing your form, you need to take the placement and appearance of form items into consideration. While the dynamic features of Lotus® Forms can make form completion simpler, more intuitive, and more interesting to complete, you need to balance those needs with your system’s performance requirements.
One easy way to reduce load and run times is to reduce the frequency in which items are moved around on the form. Load time is reduced by limiting the number of computes, while run time is reduced because you are not forcing Webform Server to refresh when the compute occurs. There are other visual cues you can use to make the form completion process easier to understand, such as having items becoming visible when relevant, or having sections change from inactive to active if the user meets certain criteria. Furthermore, if you do use visible/invisible computes to create dynamic form sections, don’t move other sections up or down the page to hide or reveal the section with the visible/invisible computes (or relevant binds). Better yet, place these sections on different wizard pages.
The following examples show the same sample form with different presentations. Each form has a spousal information section that is invisible until the "Yes" check box is selected. In the first form, the Next button has to move down to allow enough space for the spousal information to appear. In the second form, the Next button is already positioned far enough down the page for the spousal information to appear.
While having an itemlocation compute on a single button (as in the examples above) does not impact load time, moving entire sections up and down the page (as might occur in a form with a more traditional layout) can significantly increase the amount of time it takes for the form or page to load.
Exceptions to this practice
There are no exceptions to this practice.