Model Hierarchy 

Definition

Your Visual Composer model defines a hierarchy of components, which may be pages, iViews and modules. The pages and iViews in your Visual Composer model are eventually compiled into portal pages and iViews. Modules are used to organize pages and iViews in the model, in much the same way that folders are used to organize files in a file management system.

The model hierarchy also contains objects defined by the iView, such as UI components and data services.

Your model may be simple, defining a single iView. It may define a group of iViews, one page with one or more iViews, or multiple pages with multiple iViews.

 

Use

When you create a new model, you begin by adding at least one main component. For example, to begin, you might first add a page, then add iViews to the page, and then define each of the iViews. Over time, as your model grows, you may decide to group the pages and iViews into modules, to help organize and manage the overall model hierarchy. Alternatively, if you are implementing a large business package, you may begin by adding modules, and then add pages and iViews to those modules.

For more information about managing the model hierarchy, see Model Management - The Basics.