If your form contains multiple references, you can reduce the form’s load time by placing all of the "anchor" references on a single "working" page that is never displayed to the user. All reference data, such as computes, cells, and images should be stored on this invisible working page.
Large, multi-page forms often contain hundreds of references that are scattered throughout the form. This not only makes maintaining and updating references inconvenient; it can also significantly slow the time it takes to load a form. When you first open a form, only the first page and any pages it references is loaded into memory.
The more pages this page references, the more pages need to be loaded, and the longer it takes to open the form. The cycle repeats itself when you open page 2 or any following pages. If you have references pointing to and from every page, the Viewer and Webform Server will always have to load the entire form into memory before displaying it to the user. The reference model of such a form can be very complex:
Figure 1. References scattered throughout the form:
However, if you create a single working page that contains all the items and computes that you want to reference, you will never load more than 2 pages into memory: the working page and the page that will be displayed. This significantly improves loading times and simplifies the reference model:
Figure 2. References that call the working page:
The following example shows how you can reference an image for the form's banner from the "invisible" working page.
Image label on working page:
Image label on page 1 that references the image on the working page:
Image label on page 2 that references the image on the working page:
Image data on working page:
Exceptions to this practice
There are no exceptions to this practice.