Renaming Forecasting to Demand planning changes more than a term in a topic. Screenshots, translations, training, and assistant indexes may still carry the old name. Dependency-aware propagation makes that remaining work visible.
See the comparisonRoll out the Demand planning name in release 26.4 everywhere customers will see it.
The same feature is renamed in both cases. Older-release content should retain its applicable label, while current-release outputs need the new name and a route from the old term.
The topic is updated without checking dependent assets or indexes.
The German translation and assistant answers still say Forecasting, leaving customers unsure whether it was removed.
The term record and dependent artifacts have versioned relationships.
Current outputs use Demand planning and questions using Forecasting still reach the same feature.
A source edit is one small part of the rollout. The cost case depends on finding indirect dependencies and verifying the artifacts customers actually use.
Record the approved name and effective release.
Rebuild or review outputs beyond direct text reuse.
Check current answers and retained older scope.
Compare total effort for a completed change rollout, including translations, assets, reindexing, and repair.
List expected outputs before the change and record each version and verification result. Distinguish obsolete uses in current content from valid uses in historical instructions or search aliases.
Include dependency and terminology maintenance in content cost. Track support questions asking where the feature went and observe adoption separately. A successful rename rollout does not establish that more users adopt the feature.
Direct reuse updates text references. A dependency model reaches screenshots, translations, training modules, and indexes that need a different kind of change.
Apply the new name to release 26.4 outputs and preserve the old phrase as a search alias.
Use shared term references and maintained question/answer checks rather than independent copies.
Define the current preferred name, effective scope, and legacy synonyms against one stable feature identity.
Track artifacts and outputs that depend on the feature or term even when direct text reuse does not reach them.
Pilot one rename with known translated and indexed outputs. Build the dependency list, run the rollout, and test questions using both names.
Product approves the name and effective date. Publishing and search owners rebuild outputs; content and localization owners review dependent assets.
See how this scenario works
Intuitive Stack can help model terminology and output dependencies, then define a propagation check with your publishing, localization, and search owners.