Data Model
Every dashboard is represented by a server-side context that contains configuration of dashboard layout, components, bindings, and more.
At the same time, once a dashboard lifecycle is started (e.g. the dashboard is running) a separate context tree is created that represents running dashboard's data model. Each context of dashboard's context tree represents a single UI component of the running dashboard. All component contexts are added to the root of dashboard context tree, so component context hierarchy doesn't match hierarchy of dashboard's nested containers and components.
Variables, functions and events of a dashboard component's context match properties, operations and events of this UI component. Thus, addressing component context entities from dashboard bindings is effectively a process working with UI component, e.g. configuring them, reacting to their events, etc.
Was this page helpful?