Implant and Sub-Dashboard Comparison
The Sub-Dashboard and Implant containers both enable the display of a reference dashboard within another, “parent” dashboard, allowing previously created content to be reused in multiple dashboards. Although the results appear quite similar to the end user, administrators and designers must be aware of the differences between Sub-Dashboard and Implant containers, and their different use cases. The tutorials Implanting Dashboards and Using Sub-Dashboards also offer more detail on how to utilize these containers.
Implant Container | Sub-Dashboard Container | |
|---|---|---|
Function | Preprocesses a reference dashboard and implant its elements into the parent dashboard. | Creates and displays an instance of a reference dashboard within a parent dashboard. |
Common Use Case | Reuse a single display dashboard for different instances of a given context. | Displaying content dashboards within a Dashboard Template. |
Lifecycle | Preprocesses the reference dashboard, including all components, events, and bindings, and implants them into the parent dashboard. The reference dashboard does not pass through the usual dashboard lifecycle. | The reference dashboard is cloned and displayed in the parent dashboard, with the cloned dashboard passing through the its own dashboard lifecycle separate from the lifecycle of the parent dashboard. |
Hierarchy and Nesting | An Implant container cannot reference a dashboard for implant which itself contains an Implant container. Multiple Implant containers, however, can be used in a single dashboard. | A Sub-Dashboard may reference a dashboard which contains any number of sub-dashboards and Implant containers. |
Performance | A dashboard containing multiple Implant containers will general load content faster than a comparative dashboard using Sub-dashboard components instead. | Able to reference dashboards with Sub-Dashboard components, but can have worse loading times than the Implant container. |
Was this page helpful?