Dynamic baseline re-evaluation during AEM Guides publishditamap workflow
This article explains how dynamic baselines are processed during the publishditamap workflow in Adobe Experience Manager (AEM) Guides. It describes how dynamic baselines are re-evaluated at publish time, what content is recalculated, and the considerations for ensuring that published output reflects the expected repository state and baseline rules.
Description description
Environment
Adobe Experience Manager (AEM) Guides (all versions)
Issue/Symptoms
Dynamic baselines in AEM Guides are rule-based collections that determine which versions of topics and maps are included during publishing. When using the publishditamap workflow with a dynamic baseline, the system recalculates the baseline at publish time based on the current state of the repository.
- Dynamic baselines are re-evaluated during the
publishditamapworkflow, resulting in published content that reflects the latest repository state.
Cause
Dynamic baselines are evaluated according to rules such as labels, dates, or latest-version criteria. When the publishditamap workflow is executed with a dynamic baseline, the baseline engine recalculates the effective content set at publish time.
Resolution resolution
Follow the steps below to resolve the issue:
-
Ensure that a named dynamic baseline exists for the target
ditamapbefore invoking thepublishditamapworkflow. -
If you have recently changed baseline selection rules or created a new baseline, wait until any asynchronous baseline creation or update job is complete before proceeding.
-
Configure your publishing preset to use the dynamic baseline by setting the following properties:
code language-none fmdita-useBaseline=true fmdita-baselineName= -
Invoke the
publishditamapworkflow as usual. -
The workflow re-evaluates the dynamic baseline at publish time, including:
- Referenced topics (resolved according to dynamic rules)
- Indirect references (processed per configured rules and parent map/topic versions)
- Labels (such as “Latest Release”)
- Newly added or removed references (included or excluded based on the current dependency graph)
- Baseline metadata (version-selection data may be recalculated)
-
After publishing, verify that the published output reflects the expected versions and references based on the current repository state and baseline rules.