Login
Home CMS Documentation Home CMS 10 DITA Processing Pipeline DITA Properties DITA Depends-On Properties

DITA "Depends On" Properties

Prerequisites: The asset item schema type must be DITA Content. The Depends On tab displays for only DITA items.

Use the Depends On tab to view all content dependencies for your selected DITA asset, including cross-references, content references, and linked assets.

The tab displays both direct dependencies (content your DITA asset directly references) and indirect dependencies (content referenced by your dependencies). For example, if your DITA topic references another topic that contains an image, both the topic and image appear as dependencies with their hierarchical relationship indicated.

See Dependencies Overview for more details about DITA dependency linking.

Version Notes: CMS 10.6.378+ vs. CMS 10.6.308–10.6.342
Dependency tracking differs between CMS 10.6.378 and CMS 10.6.308–10.6.342.

  • CMS 10.6.378+: Tracks dependencies for the DITA asset's latest content version and versions marked to publishing targets. Use the Dependency Version drop-down to filter by version.

  • CMS 10.6.308–10.6.342: Tracks dependencies only for the DITA asset's latest version. Changes made and saved in the asset's Edit tab immediately updates the Depends On list, regardless of check-in/out status. The CMS does not account for dependencies in marked older versions of the DITA asset.

See CMS DITA Versioning Functionality for more details about CMS 10.6 dependency functionality changes.

To review DITA content dependencies:

  1. Navigate to Assets > Assets Tree.
  2. Select the DITA asset, then click the DITA Properties > Depends On tab.
    The Depends On tab displays dependencies for the selected DITA asset.
  3. Choose one of the following filter options.
    OptionDescription
    Direct DependenciesDisplays only assets directly referenced by your DITA asset (distance 1 dependencies).
    All DependentsDisplays all dependencies in the hierarchy, including indirect dependencies (child, grandchild, and deeper relationships).

    This option becomes inactive when your DITA asset has no dependencies.

    DITA Properties > Depends On Tab

  4. Select or clear the Show Errors Only checkbox.

    If selected, this option displays only dependencies with errors Validity Error Icon.

  5. Select a version filter from the Dependency Version drop-down:
    Version Notes: CMS 10.6.378
    This step only applies to CMS 10.6.378+. Skip this step for CMS 10.6.308–10.6.342.

    Filter the DITA asset's dependencies by latest version or by a version marked to a publishing target.

    OptionDescription
    Show AllDisplays all dependencies for the DITA asset, regardless of version or publishing target.

    Thia option includes dependencies referenced in the Latest Version and any version o marked to publishing targets.

    Empty results indicate no dependencies exist in the latest version or marked-for-publish versions.

    Latest VersionDisplays dependencies from the latest content version. The Dependency Version column indicates publishing targets where this version is marked.

    This version filter includes any dependency changes saved but not checked in to the DITA asset.

    Empty results indicate no dependencies exist in the latest version.

    Name of Publishing TargetDisplays dependencies only from the version marked to your selected publishing target.

    Publishing target filter options display with the publish icon .

    When the latest version is marked to a target, only the latest checked-in changes for that target are included.

    Empty results indicate the selected DITA asset is either not marked to the target or the marked version has no dependencies.
  6. Optional: Enter keywords in the Search field to search for individual dependencies by Name, Dependency Route, or Type.
  7. Review the dependencies within the list.

    Data includes:

    Data Type

    Description

    NameFile name, file extension, and ID of the asset item referenced.
    Tip
    Click the file name to navigate to the referenced asset.

    Distance

    		Hierarchical relationship distance from your selected DITA asset to the dependency.

    Examples:

    • Distance 1 = direct reference in your DITA content (child relationship).
    • Distance 2 = referenced by a direct child dependency (grandchild relationship).

    Note
    You can select the All Descendents filter option to display all dependencies, including those with distances greater than 1.

    Dependency Route

    Path from your DITA asset to the dependency based on the reference hierarchy. This route indicates where the DITA assets reference the dependency within the hierarchy.

    For example, let's say the DITA asset rinsingthecar.dita is a dependency with the following route:

    garage-1.ditamap/washingthecar.dita/rinsingthecar.dita

    In this example, garage-1.ditamap (the selected DITA asset) references washingthecar.dita, which references rinsingthecar.dita.

    Version Notes: CMS 10.6.308–10.6.342
    In CMS 10.6.308–10.6.342, select the All Descendants option to display dependency routes.
    Type

    DITA element type that references the dependency (e.g., xref, conref, keydef) .

    Confirmed
    Version Notes: CMS 10.6.378 vs. CMS 10.6.308–10.6.342
    Confirmed column removed from CMS 10.6.378+. This column only displays in CMS 10.6.308–10.6.342.

    The Dependency Confirmed for Publish checkmark indicates the system has registered the dependency and will include it in the next publish.

    The pipeline requires all dependencies to be confirmed before publishing.

    Note
    You can only publish DITA content from the map level. See Publishing DITA in Ingeniux CMS for details.

    Confirmation factors include:

    • Publishes exclude unconfirmed dependencies. However, if the Show all pages preview option is selected at the time of preview generation, DITA Preview includes them.
    • All dependencies of newly created assets remain unconfirmed until you check in those new assets.
    • If you or other users add dependencies to checked-out assets, the new dependencies remain unconfirmed until checked in.
    • Removed dependencies from checked-out assets remain confirmed until checked in.
    Dependency Version
    Version Notes: CMS 10.6.378+
    The Dependency Version column is only available in CMS 10.6.378. This column indicates the DITA asset version where each dependency is referenced.

    You can filter the Depends On list to only display dependencies for a particular version by using the Dependency Version drop-down list.

    ValidityError icon Validity Error Icon displays for dependency conflicts. Hover over the icon for error details. See DITA Dependency Validity Errors for troubleshooting details.
    Version Notes: CMS 10.6.378+
    CMS 10.6.378+ displays errors for unresolved assets, dependencies not marked to publishing targets, and dependencies in the Recycle folder. Use the Show Errors Only filter to display dependency conflicts before running DITA publishes or previews.
    Last ModifiedDate of last changes made to the dependency.
    Version Notes: CMS 10.6.492
    This column is available only in the CMS 10.6.492.
    Modified By User who last made changes to the dependency.
    Version Notes: CMS 10.6.492
    This column is included only in the CMS 10.6.492Depends On tab.
  8. Optional: Click Download CSV to export the dependency data as a .csv file.
    Note
    • The export only includes data based on your filtering selections. For example, selecting Direct Dependents, exports only direct dependency data.
    • The Download CSV button is inactive when the Show Errors Only checkbox or Search filters are applied. Clear these filters to enable download.