Modeling Portal Content 

This section describes the tasks involved when modeling portal objects in Visual Composer. It includes the following topics:

·        Creating Portal Content Objects

Explains how to create models for new, standard portal objects

·        Creating Business Suite Content

Explains how to create models according to the template-based Business Suite rules

·        Reusing Existing Components

Explains how to reuse existing components from runtime as well as design-time repositories

·        Working with Reused Components

Explains how to work with content that is reused.

·        Defining OBN Targets

Explains how to add object-based navigation when modeling pages and iViews

Managing Models

Use the core Visual Composer tools to perform basic management operations with your portal content models, such as creating, opening, saving, closing models, deleting, and using the source control capabilities of NWDI. For more information, see Managing Models.

Before deleting a model, check that it is not reused by any other model. Deleting a model may adversely affect the expected behavior of another model that is referencing it.

Translation

For portal content modeled in Visual Composer, the static values defined for the following Visual Composer model properties are automatically tagged for translation and entered automatically into an XLF file:

●      Name - The corresponding property for the portal object, after deployment, is Title.

●      Description - For the portal object, the property is also Description.

More information, Preparing Models for Translation.