Publishing configuration

The Experience Edge publishing process can be configured by the use of the following settings:

Publish related items
Related items are items referenced by the item being published (such as datasources, media, templates, renderings, layouts, partial designs, etc). The Publish related items checkbox can be found in the Publish item dialog in the Content Editor that appears when you are publishing a single item. When this setting is enabled, all related items will be published. We recommend enabling this setting, as it ensures all related items are properly updated during the publishing operation. When disabled, only the selected item is published. For more on how related items and dependencies affect the publishing process, see Dependencies and publishing.

Publishing.DeepScanRelatedItems
Publishing.DeepScanRelatedItems interacts with the Publish related items setting. When Publish related items is enabled, Publishing.DeepScanRelatedItems controls how deeply the system scans for related items during publishing.

When Publishing.DeepScanRelatedItems is set to true, the system recursively collects all related items: first gathering items directly referenced by the given item, then items referenced by those items, and so on down the chain. When set to false, only directly referenced items are included as related items.

For example, if you have an ItemA that references Item1LR, and Item1LR refences another item, Item2LR (when Item1LR and Item2LR have been not been previously published), the following table shows which items will be published:

ExperienceEdge.IncludeDependencyAncestors
When enabled, this setting stores parent-ancestor relationships so that changes to parent items can trigger republishing of dependent items. When disabled, those upward relationships are not considered.

This setting controls whether an item's ancestor pages are included in its Edge entity metadata. When enabled, every time an item is published, all of its dependencies are checked to determine whether they also need to be republished.

For example, if item X is a child of parent A, which is a child of parent B, and ExperienceEdge.IncludeDependencyAncestors is set to true:

• If parent A is modified, all items that depend on parent A will be republished.

• If parent B is modified, parent A and item X will be republished as a result.

ExperienceEdge.ComputeContentDependencies
When enabled, this setting builds dependency links between items (for example, datasources or linked items), so that updating one item can trigger republishing of dependent items. This setting interacts with another setting, ExperienceEdge.MaxSerializationDepth, which specifies how many levels will be scanned for dependency links. For example, when ExperienceEdge.ComputeContentDependencies is set to true and ExperienceEdge.MaxSerializationDepth is set to 4, then SitecoreAI will scan 4 levels deep. If ExperienceEdge.MaxSerializationDepth is set to 0, then it will not scan for dependency links at all.

ExperienceEdge.MaxSerializationDepth
This setting specifies the maximum number of levels that will be scanned when building dependency links between items. It interacts with ExperienceEdge.ComputeContentDependencies (see the previous entry). The default value is 4.

ExperienceEdge.LinkDependentTypes
This setting defines which field types count as dependencies. It affects whether referenced items are included in dependency tracking and can trigger republish.

ExperienceEdge.EnableItemLanguageFallback
When this setting is enabled, fallback language versions are considered during publishing, which can cause additional versions to be published or republished.

ExperienceEdge.EnableFieldLanguageFallback
When this setting is enabled, field-level fallback values are included and can affect what data is published and when items are republished.