Documentation Center

Reusing Non-controlling Container objects

When you reuse a Container object in the hierarchy, note that any changes to the container are reflected in all the same, reused containers.

This means that if you add or delete an object from the container anywhere in the hierarchy, all the same, reused containers, throughout the hierarchy are affected.

Reusing Container objects within the hierarchy

When working within the hierarchy and outside a Project or a ContentRoutingProject, modifications to a Container object take effect immediately (and do not require Posting). Additions or deletions to a reused container affect all the same, reused containers throughout the hierarchy.

Example

Reusing Container objects into a standard project or ContentRoutingProject

When reusing Container objects into a standard Project or ContentRoutingProject, the type of container that is reused affects the outcome of posting. If you reuse a Group or Folder Container object in a standard Project or ContentRoutingProject, note that they do not post.

The important implication of the Group and Folder objects not posting is if they are reused into a standard Project or ContentRoutingProject, changes made to the Group or Folder objects are not recognized and therefore are not updated when the standard Project or ContentRoutingProject is posted. This includes:

  • changes to the Group or Folder object itself

    This includes changes such as adding a Global Note or modifications to the object’s Property Sheet.

  • changes to the child list

If new objects are added, or if objects are deleted in a reused Group or Folder Object in a standard Project or ContentRoutingProject, they are not posted to the Group or Folder object in the Configuration.

When a new object is posted, if created in a Group or Folder in a standard Project or ContentRoutingProject, note that it will not have a parent under which to post—it posts directly under the Configuration object, and not under the Group or Folder object in the Configuration

Example

Reusing Document containers into a standard project or ContentRoutingProject

Modifications to a Container object that posts, such as a Document container, are reflected in all the same, reused containers in the hierarchy when the standard Project or ContentRoutingProject is posted.

This means that when the standard Project or ContentRoutingProject is posted, any object that was added to, or deleted from a reused (posting) container such as the Document container, it is added or deleted in all the same, reused Document containers throughout the hierarchy.

Example