Include external views in tab pages without frames

Standard tab pages that include nested views (as opposed to nested panels) using the file attribute display included views inside an iframe. This is a safe approach, but it increases the server CPU utilization and the view loading latency because each frame must render and load the complete view.

Adding nested panels to tabs improves the performance but may create a maintenance problem - the tab view may become too large and complicated.

Another option that improves the performance but keeps tab page content in separate AXVW files is the tab/@useFrame attribute. By default, when not specified, its value is true and the tab page uses a frame. When you explicitly specify useFrame = false, the nested tab page views are included on the server into the master HTML page.

<tab name="exTabsNested_page2-2" file="ab-ex-tabs-nested-page.axvw" useFrame="false">
<title>Review Action Details</title>
</tab>

When frames are not used, all included content should be designed to avoid naming conflicts. All panels and data sources in all nested tab page views must use unique IDs (and not default IDs), and all JavaScript functions and variables must have unique names.

View: http://localhost:8080/archibus/schema/ab-products/solutions/assemblies/tabbed-views/ab-ex-nested-tabs.axvw