Scopes and alerts on scopes
Scopes can be defined on grid FDFs, and you can also alert a scope from scripting for a chart FDF. The point where a scope is defined marks the top level in the subtree of the object model where it can be used. Collection-based FDFs below this point can be registered as alert listeners on the scope.
For security, alert listeners to a scope can only be registered/unregistered through server-side APIs. This prevents clients from altering the listeners.
Scopes are added and removed on the Scopes tab in the FDF Editor.
Error handling
When alerting listeners on a scope, if a scope cannot be found, the AlertListenersOnScopeFail diagnostics warning is logged and the alert is ignored. This warning is also logged if the FDF cannot be found, and the FDF is removed from the list of listeners.
When registering or unregistering an alert listener to a scope, if a scope cannot be found, the AlertListenerOnScopeRegistrationFail diagnostics warning is logged.
Scope inspection
You can inspect scopes defined on a grid FDF using Inspection Mode on a portal page.
While inspecting a page, the Grid FDF section shows any scopes that are defined on the grid. It also shows in brackets any scopes that are accessible. When you move the cursor over an accessible scope, a "Go to definition" tooltip is displayed and the cursor changes to a pointer. You can click the accessible scope to open the FDF where the scope is defined. The first cell inside of the grid is chosen, and the inspection location is pinned.