← Back to Roadmap

Release Manager - Frontend

0 features

📋 Description

The release manager enables controlled exposure of content to external systems by using recipes and metadata to determine what is released and to whom. It makes it possible to overview content delivered by external systems to the platform and align it with recipe based structures. It ensures that only the right content is made available, supporting targeted, efficient, and automated content distribution across channels and markets. The release manager is where the shift from "publication focused delivery" to "product focused delivery" can be done.

💎 Business Value

Reduces distribution errors and manual effort while ensuring the right content reaches the right channels and markets with traceable, automated delivery in a product focused manner.
⚡ Active development branch

📐 UX-Specification Resolved  View in Azure DevOps →

📖 Frontend User Stories (5)

User stories linked from other projects

📖 Pre-Publishing Authoring Validation (Release Manager)

Committed

As an author, I want pre-publishing validation to detect authoring errors (especially invalid links) before output generation so that I can correct issues immediately and avoid time-consuming troubleshooting during publishing. Business Value * Prevents publish-time failures by catching defects earlier in the authoring flow. * Reduces troubleshooting effort and turnaround time for release teams. * Improves output reliability and confidence in downstream delivery.

View in Azure DevOps →

📖 Topic-to-Topic Linking (Authoring in CCMS) (Release Manager)

Approved

Title: Create and manage topic-to-topic relationships in CCMS Story Statement:As a Content Engineer, I want to create and maintain links between topics (including many-to-many and reciprocal links), so that related content is explicitly connected and discoverable in the CCMS Business Value: Restores/modernizes relationship-table capability. Improves navigation and reuse across related topics. Reduces manual tracking of topic relationships.

View in Azure DevOps →

📖 External Target On-Demand Output and Metadata Deployment (Release manager)

Committed

## Story Statement As a publishing operator, I want to deploy outputs and metadata to predefined external targets on demand so that downstream business systems can consume updates reliably without manual transfer steps. ## Business Value * Improves interoperability with AGCO enterprise systems. * Reduces manual transfer steps in downstream delivery. * Increases reliability of automated data exchange.

View in Azure DevOps →

📖 Downstream Propagation of Topic Links

Approved

Title: Propagate topic relationship changes to downstream systems Story Statement:As a Publishing/Integration Manager, I want topic-link relationship changes from the CCMS to propagate reliably to downstream systems, so that end users receive consistent, up-to-date cross-topic navigation. Business Value: Keeps downstream outputs aligned with CCMS relationships. Ensures downstream outputs navigate correctly. Reduces manual rework and integration drift. Improves trust in published relationship data.

View in Azure DevOps →

📖 Filtered Publishing (Release manager)

Committed

## Story Statement As a IA, I want to apply profiles and classifications to content and recipes so that each output variant matches the intended product configuration. ## Business Value - Improves publishing throughput and release predictability. - Reduces output defects across variants and formats. - Strengthens downstream readiness with consistent publish artifacts.

View in Azure DevOps →

📋 Frontend Requirements (2)

Related requirement tasks from other projects

✓ 3.70 - System provides HTML outputs.

To Do

Description Please list them (HTML, HTML5, zip, archive, Help files)? Platform Status: PPT Status: MVP: Yes Must Have: Priority 1 (A)

View in Azure DevOps →

✓ 3.37 and 3.36 - System can deploy content to external targets and locations, such as web servers file systems, databases, and other targets.

To Do

Description Platform Status: PPT Status: MVP: Yes Must Have: Priority 1 (A) Use Case Does your system deliver to Salesforce knowledge or have a supported connector? Notes Merged with 3.36 - print and digital.

View in Azure DevOps →