External Target On-Demand Output and Metadata Deployment (Release manager)
Approved
#3401
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.
Acceptance Criteria
- Given predefined external target configurations exist, when a user initiates deployment, then outputs and metadata are delivered to the selected destinations.
- Given deployment outcomes are reviewed, when logs are checked, then success, failure reasons, and retry details are available.
Filtered Publishing (Release manager)
Approved
#3402
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.
Acceptance Criteria
- Given profiling and filtering rules are configured, when outputs are generated, then only matching content is included.
- Given variable-driven terms are defined, when variants are produced, then variable substitutions are correct.
- Given complex product hierarchies, when selection criteria are applied, then output scope reflects chosen configuration.
- Given a release references specific versions, when publishing runs, then the configured version-selection rules are applied consistently.
Topic-to-Topic Linking (Authoring in CCMS)
Approved
#3368
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.
Acceptance Criteria
- Given an author links topic A to topics B and E, when changes are saved, then all relationships are persisted and visible in the CCMS.
- Given relationships are configured, when validation runs, then the system supports or rejects them according to defined business rules with clear feedback.
- Given users view a topic relationship list, when the topic is opened, then inbound and outbound links are traceable and accurate