Creating Portal Content Objects 
Use Visual Composer to create and model portal content objects. You can model roles, worksets, pages, iViews, and Business Suite containers, work centers, and views.
You can also add applications to models: either reuse existing portal components and portlets or create applications within your model using the Visual Composer composite view components.
Prerequisites
See Getting Started.
Procedure
Choose
Model 
New 
or drag a portal content element icon from the Compose Model panel onto an existing, open model.
NoteDragging element icons onto existing open models follows logical workflow rules. Each component, which is a potential drag target, displays text indicating what may be dragged onto it. For more information, see the tables in Reusing Existing Components.
End of the note.If you created a new model, in the Create New Model dialog box, choose Portal Modeling from the Project Type panel, choose a portal object model from the Model Type panel, and supply the required information.
From the Development component dropdown list, choose the development component in which to store the model.
You can choose an existing development component from the list or you can click New and create a new development component.
NoteTo create a development component (DC) with a unique name, it is possible to add a prefix, using one or more slashes (/) to before the DC name. The entire DC name, including the prefix, is limited to 40 characters.
Note that the portal does not support the slash in folder names and deployment converts the slashes to periods (.).
End of the note.
CautionWhen naming a model, avoid special characters that are not supported by the naming conventions for development components (DCs).
End of the caution.Except for iViews, this is all the input required. If you choose to create an iView model, the iView Templates dialog box opens and additional information is needed:
iView Template
Parameter
URL iView
Description (optional)
ID (supplied, read only)RL to iView target (required)
URL to iView target (required)
Dynamic URL iView
Description (optional)
ID (supplied, read only)
URL to iView target (required)
URL parameters (required, UI supplied for adding parameters and their values)
NoteTo change parameters, or their values, in an existing dynamic URL iView, go to the Configure task panel of the iView and, in the URL Template field, edit the URL directly. The format is as follows:
http://url1?param1name=<Request.param1value>¶m2name=<Request.param2value>
End of the note.Service Map iView (for Business Suite)
Description (optional)
ID (supplied, read only)
Related Services iView (for Business Suite)
Description (optional)
ID (supplied, read only)
SAP Transaction iView
Description (optional)
ID (supplied, read only)
System (required)
SAP GUI Type (required)
Transaction Code (required)
BEx Web Application iView
Description (optional)
ID (supplied, read only)
System (required)
Version (required)
Bex Web Application Query String (required)
Choose OK.
The model is created and a tab, labeled with the model name, appears on the Portal Layout board.
You can open multiple models and use the tabs to switch between them to continue working with a specific model.
NoteTo edit properties of an element that you created within a higher level, existing model, such as an iView within a page or a workset within a role, or to work on a composite view application created within an existing model, you need to drill down into the required model or composite view. More information, Working with Reused Components.
End of the note.Save the model, deploy it to the portal, and, if relevant, check it into the DTR.
NoteTo create a title for your object, which appears in the Portal Catalog after deployment, choose Rename from the context menu of the model's tab and enter the string you want the deployed model to display in the portal.
End of the note.
Folders Created with Portal Content Modeling
General Information
To create a folder you drag the folder icon into a role, workset, or another folder.
To add content, folders, worksets, or roles to an existing folder, visible in the Detailed Navigation area, drag drop the relevant icon to the folder.
The child objects with which you can populate a folder depend on the rules of the parent object. For example, a folder within a role can contain worksets, but a folder within a workset cannot contain a role.
You can order content within a folder by dragging it up or down, but you cannot drag content between different folders. This is also relevant to worksets and roles in a tree.
Information Specific to Business Suite
You can create folders under Related Services, but not in the Detailed Navigation area of the navigation panel.
You can add only iViews and pages to folders.