If your form contains multiple pages, the load time can be reduced by loading a specific number of pages when the form is opened, rather than the entire form.
When users attempt to access multiple-page forms, they may experience a delay as the entire form must be loaded. The pageloading
option allows form designers to determine how many pages of a multiple-page form are initially loaded. However, you can decrease the amount of time users must wait by using the pageloading
option. This results in faster load times for users.Using page loading can significantly decrease the amount of time it takes to open a form, however it may increase the amount of time required to switch to a new page, as the page must be loaded into memory before being displayed.
allows a form designer to specify exactly which pages are loaded when the form is opened. Typically, you would specify the first page of the form, the working page that contains all references and any particularly large page that takes a long time to load.
XFDL compute references to items on pages which have not loaded will fail. For this reason you should either avoid compute references to unloaded pages, or specify the referenced pages to be loaded in advance with the autoload option. The XForms data model is always loaded, even when page loading is enabled.
The following example enables page loading and specifies that PAGE1 and workingPage should be loaded into memory when the form is opened. This sample also requires all of the unused pages to be loaded into memory before actions of type submit and signature are performed.
Exceptions to this practice
There are no exceptions to this practice.
Back to: Performance best practices