Heretto CCMS 2026.09.11: Next-Gen Infrastructure

• Unified backend architecture. One modern backend now powers the entire platform, unlocking a new level of speed and flexibility for everything built on top of it. Our legacy infrastructure for Heretto CCMS relied on 8+ separate backend components, each with its own limitations and maintenance needs. Next-gen infrastructure consolidates all of it into a single, modern architecture, removing a major source of complexity and lifting the technical ceiling that previously blocked capabilities like Insights and Find & Replace.

• Added: Find & Replace. Search a branch, folder, or map across all your XML files at once, then refine with options like case, whole words, or a specific element or attribute, up to regex and XPath. Find is available in Beta now, and Replace follows in a later phase. See Find & Replace (Beta).

• Added: Insights (Beta). Analyze your content at scale across a branch, folder, or map with three new reports: Content for what's in your content set, Localization for translation progress, and Reuse for how much content is shared. See Reports (Beta).

• Added: Quality Report (Beta). Scan a map or folder on demand to find broken links, invalid structures, and metadata errors, ranked by severity and tracked over time. See Quality Report.

• Added: Extracted Metadata (Beta). Pull values that already exist in your DITA files into reports for filtering, without adding anything to the files themselves. See Metadata Governance in Heretto CCMS and Extracted Metadata Configurations.

• Added: Delivery Maps. Mark the maps that represent complete deliverables, such as a user guide or help center, so reports measure those instead of every map in your content set. See Delivery Maps.

• Added: Localization API. A new set of endpoints for managing localization work programmatically. Documentation is coming soon.

• Added: Commit-Scoped File Changes. The REST API can now group related file changes into one commit, so they appear together in the activity feed and resource history with a single message. Documentation is coming soon.

• Enhanced: Search. Search inside the file, not just its title and file name, by selecting full-text in the search bar drop-down, and find a topic or map by its DITA id attribute value. Saved searches and sorting in the search bar drop-down are also now available. Updated docs are coming soon. For current docs, see Search.

• Enhanced: Scalability. The platform is ready to grow as big and as fast as your content strategy demands. Next-gen infrastructure supports a 100x increase in scalability, so teams can grow content volume and manage multi-brand rollouts without hitting platform limits, now or as they scale further in the future.

• Enhanced: Delivery speed. Customers get fixes and enhancements faster than ever. A simpler, modern backend shortens the path from backlog to production, so engineering moves bugs through the pipeline faster and support resolves issues more quickly.

• Enhanced: Stability. The platform runs with a new level of predictability and confidence. With the next-gen infrastructure, whole classes of bugs and edge case failures are designed out at the source, meaning fewer disruptions for every team relying on the CCMS.

• Enhanced: Recovery time. When the unexpected happens, the platform bounces back faster than ever. It's built for high availability, so it keeps running even if individual components fail. Disaster recovery is also faster and more reliable. Together, these improvements cut emergency maintenance time by 96%.

• Enhanced: Branching performance. Branching now happens at a speed that changes how teams can work. For example, large operations that used to take around 13 hours now complete in around 15 minutes, a 50x improvement, making it practical to branch large content sets without disrupting a team's workflow.

• Enhanced: Localization processing. Localization now moves at a pace that keeps up with even the most demanding release schedules. Processing speed has improved 100x, shortening the path from source update to localized, publish-ready content.

For more details about the Next-Gen Infrastructure, including migration details, changes you can expect, and FAQs, see Next-Generation Infrastructure for Heretto CCMS.

Heretto Deploy API 26.09.11

• Fixed. We fixed a short-lived issue where content requests made with JSON Web Tokens (JWTs) that had no audiences claim, or that had the claim set to null, incorrectly returned __default audience content even when a different audience was requested. This affected both manual and active sync deployments. Tokens with no audiences claim or a null claim now correctly return the content of the requested audience, since a missing or null claim places no restriction on which audience can be accessed. Tokens with an explicitly empty audiences claim continue to return __default audience content regardless of which audience is requested, since an empty claim restricts access to __default. For details on Deploy API authentication, see Deploy API Authentication.

Anew CCMS version with a number of important fixes is now ready!

Heretto CCMS 26.09.04

• Fixed. We fixed an issue where opening a sitemap in the Content Editor could take significantly longer than expected. Sitemaps now open without the added delay.

• Fixed. We fixed an issue where a user could open and modify a DITAVAL file in the Content Editor even when their group was denied write access to that file. Write permissions are now enforced for DITAVAL files.

• Fixed. We fixed an issue where generating a PDF preview with PDF Generator could fail for some maps, even when publishing the same map succeeded. PDF previews now generate as expected.

• Fixed. We fixed an issue where bundling large maps for publishing to a third-party platform with DITA Open Toolkit (DITA-OT) could produce an incomplete bundle. This occurred when a topic contained a tracked change recording the removal of an attribute from an xref element. Bundles now include all expected files and publishing completes as expected.

• Fixed. We fixed an issue where publishing a localized map with DITA Open Toolkit (DITA-OT) failed when a topic in that map used a content-reference (conref). The conref target was not resolved to the localized copy of the file, so the publish ended in an error. This affected all localization types, and publishing the same map with PDF Generator succeeded. Localized maps containing conrefs now publish with DITA-OT as expected.

• Fixed. We fixed an issue where the trans-unit elements in XLIFF files generated by a localization job were listed in a random order rather than following the content order of the original topic. Now, XLIFF files preserve that order.