Restrictions on Runtime Functionality

For deferred panes, you may observe a few restrictions on runtime functionality.

Handling Bindings to Deferred Panes and Child Controls

  • If the Defer Initialization check box is cleared, then bindings, script references, and computation action references to the pane and its children are not affected.
  • If the Defer Initialization check box is selected, then any references to child or nested controls using scripts or computation actions are flagged with an error-level problem marker. You can make use of events tied to the pane and its children in rule definitions. Binding to panes are always active and working, but the bindings to child and nested controls are inactive until the pane and child controls have been fully initialized.
  • If the Defer Rendering check box is selected, and the Defer Initialization check box is cleared, bindings to panes and controls are active even if the pane is not currently rendered. The internal model of the pane or child controls can be updated using scripts, bindings, or computation actions. The effects of such updates are visible after the pane is rendered.

Handling Validations in Deferred Panes

An un-rendered pane is treated the same as an invisible pane with respect to the suppression of validation checking.

Loading Deferred Panes

Panes marked to use deferred rendering display a spinning wheel to indicate that the content is being initialized. This loading indicator is visible only if there is a noticeable delay in rendering the pane.