AlertComponentFilterChanged

Initial rendering

This describes the behavior of alerts/filter changes when a component is rendered during the startup sequence. This happens when the page is first loaded or when a component is rendered for the first time when the rendered property is changed to true by scripting.

Order of events:

• Server-side layout initializing
• Server-side filter changed
• Client-side layout initializing
• Done

There is no client-side filter changed event during the startup sequence.

Layouts that have not been rendered (for example, pre-startup) ignore all alerts and filters received. However, there is an ambient filter that is passed to the initial server-side filter-changed handler. Usually this comes from the URL of the page translated through the definition of the IPFGrid or IPFChart FDF. However, if Rendered? is set to true and a filter-changed event is received, this filter becomes the ambient filter that the first server-side filter-changed handler receives.

To pass parameters to a layout right after setting Rendered? to true, call AlertComponentFilterChanged() and set Rendered? = true on the component. The filter payload can then deliver whatever initialization options are necessary.