Shared Maps

Shared maps enable you to easily add every warehouse topic to the deliverable maps.

Overview

Shared maps ease the effort needed to reuse content because you don't need to manually add all warehouse resources to each map.

Figure 1. Shared Map Structure.
The following example shows that:
  • Element warehouses are added to maps through topicref elements
  • Variable warehouses are added to maps through keydef elements with a @keys attribute assigned
Shared map structure
Figure 2. Shared Map Implementation.

The following example shows a shared map reused in two deliverable maps. The shared map reference in the deliverable map has the @processing-role="resource-only" attribute assigned to exclude the shared content from the deliverable map's publishes.

Shared map implementation

Guidelines

Keep the following guidelines in mind when working with shared maps:

  • Use a singular shared map.
  • Keep the shared map and the warehouse map in a dedicated folder in the Content Library. For example, keep them in the _shared folder.
  • Include every warehouse topic in the shared map.
    Important: This does not apply to the “Context-Specific Variables Strategy” described in Variable Warehouse Topics.
  • Add the shared map to every deliverable map with the @processing-role="resource-only" attribute.
    Tip: We can configure your shared map to be included in every new map that you create in Heretto CCMS by updating your map templates. For more information, contact you Customer Success Manager.