The Contenta Hierarchy

Note the following about the FrameMaker files, Contenta objects, and the Contenta Explorer hierarchy.

  • Store the FmDoc and FmBook objects in a container object under the Configuration object. (This container object does not have to be a direct child of the Configuration object.)
  • The container with the graphics that are referenced in the FrameMaker files must be located at the same level (and have the same parent object) as the container with the FmDoc and FmBook objects and must be named Graphics.
  • A unique parent container object must be created (manually or through DI) for each FrameMaker book.
  • The order of the chapters is managed by the FrameMaker book file. This means that the order in which they appear in the hierarchy does not affect the book file. Changes made in the Contenta hierarchy using the Contenta Explorer Reorder option are not reflect in the book file and do not affect files during any consecutive export of the files.
  • Deleting the FMDoc object or a graphic object in the Contenta Explorer does not result in an update to the corresponding book or chapter object.
  • When using Projects for data modification and workflow, include the Graphics container in the Project with the FrameMaker (container) objects to be modified.

    If the Graphics container is not included in the Project, graphics are not exported into the checkout directory with the FrameMaker data. They cannot be displayed in the FrameMaker editing session and if not available at the time of editing, the FrameMaker (.fm) file loses the reference to the graphic(s)—in this case, the document contains grey blocks where the graphics were located and it is stored as such (with the grey blocks) with the link/references to the graphics removed.

    To avoid problems it is recommended that you reuse all contents of your document, that is, the data container and the graphics container, into the Project object.