Lifecycle

Once a dashboard is opened by a user within a Web UI usage session, an instance of this dashboard is created within Iotellect Server and its lifecycle is started.

Structure of dashboard lifecycle is highly dependent on whether caching is enabled for particular instance.

Lifecycle of a Non-Cacheable Dashboard

Lifecycle of a dashboard that doesn't use caching is simple and straightforward:

  • Dashboard is launched
  • Startup bindings are executed
  • Dashboard is displayed in browser window
  • shown event is fired in dashboard's root context
  • Dashboard is running
  • Another dashboard comes into the foreground
  • Dashboard is hidden
  • Dashboard's binding processor is stopped, dashboard is shut down

    • Dashboard main operation phase is terminated once another dashboard comes into foreground. It may happen in the following cases:

    • For top-level dashboards, a link is clicked or another method is used to redirect user to another web page and browser URL is changed
    • For sub-dashboards, a container that contains this sub dashboard (e.g. a tab of a tabbed panel) is hidden

    However, dashboard's main operation phase continues if a browser tab is switched by a user.

    Lifecycle of a Cacheable Dashboard

    Lifecycle of a cacheable dashboard assumes that a dashboard operation can be paused and re-started multiple times:

  • Dashboard is launched
  • Startup bindings are executed
  • Dashboard is displayed in a browser window
  • shown event is fired in dashboard's root context
  • Dashboard is running
  • Another dashboard comes into the foreground
  • Dashboard is hidden
  • Dashboard's binding processor is stopped, dashboard is paused
  • If dashboard cache is overflowing, dashboard is shut down
  • If dashboard comes to the foreground again, the lifecycle repeats from step 3 (dashboard is displayed in a browser window)

    • Cached dashboard is re-used when it comes to the foreground in one of the following cases:

    Was this page helpful?