Assigning a Unit Object to a Parent Object

Context

Packages, worksets, roles, and pages are portal objects that can contain other object types. For example, roles typically contain worksets, and pages contain iViews.

To add a portal object to a larger, "parent" object - such as a workset or role - first open the parent object in its respective editor, and then add the object from the Portal Catalog.

Note

When you add an object to a parent object, it becomes a delta-link instance of the object from which it is derived.
While portal objects are displayed in the Portal Catalog, the objects added to a parent object are not. To view the objects added to a parent object, open the parent object in its respective editor.
To determine the source objects of an object contained in a parent object, use the delta link tracer. For more information, see Tracing Delta Link Dependencies .

For more information about object instance types and how they relate to one another, see How Are Portal Objects Linked? .

Procedure

Open the parent object in its primary editor. For more information, see Editing Portal Objects .
In the Portal Catalog, from the context menu of the object that you want to add to the parent object, choose the appropriate Add option.
- To add iViews and pages to create a page, see Adding Content to a Page .
- To add objects to roles and worksets, you use the controls within the editor, although you can also add objects from the Portal Catalog and from the Detailed View as well. For more information, see Adding and Editing Content in Freestyle Roles and Worksets and Adding and Editing Content in Workcenter Roles .
- To add iViews, pages, roles, worksets, systems, and layouts to a transport package, see Adding Content to a Transport Package .

Next Steps

For information about adding portal objects as delta links or copies, see Adding an Object as a Delta Link or as a Copy .