A new CCMS content view and an update on what we've been focused on behind the scenes.

Heretto CCMS 26.02.24

• Added. You can now view the raw source content for any file type from the CCMS interface by pressing Alt and clicking the REST URL. This is especially helpful when troubleshooting, for example, publishing issues. See View DITA Content and Metadata for a Resource.

• Behind the scenes, we've been working on the next-generation Localization Reporting, Content Metrics Reporting, and Content Quality Reporting. We'll share more soon.

A new Deploy API version with a recently introduced fix to the Heretto Portal authentication flow.

Heretto Deploy API 26.02.23

• Fixed. We resolved an issue where the Heretto Portal returned a 404 error instead of a 401 for unauthorized pages, which prevented the authentication flow from triggering. The root cause was a Deploy API update that caused the appname attribute in resourceId to interfere with page resolution. After this fix, the appname attribute is ignored and no longer affects portal behavior. To learn how to use resourceId to create peer links, see URL (Peer Links).

Heretto Deploy API 26.02.19

• Added. Deploy API now supports the DITA 1.3 appid and appname attributes on the resourceid element, in addition to the existing id attribute. Either id or appid is required; appname is optional. The resourceid element is now also supported in topicmeta, not just prolog. If multiple topics share the same ID value in the resourceid element (not recommended), navigating to a topic by its resource ID returns the first topic in the sitemap.

  For more information on the resourceid element, see resourceid (DITA 1.3 Specification). To learn how to use resourceId to create peer links, see URL (Peer Links).

• Added. The Deploy API now extracts resourceid metadata from both prolog and topicmeta elements and serves it to consuming endpoints, including Heretto Portal and third-party integrations. The resourceid metadata is included in the Get content and metadata for a page endpoint in the resourceIds property. A single topic can carry multiple resource IDs, and searching any one of them will return that topic. While sharing a resource ID across multiple topics is not recommended, if this occurs, all matching topics are returned in search results but users are always taken to the first topic in the sitemap.

  Deployments using active sync will reflect this change automatically. Manual deployments require a republish to reprocess the metadata.

  For more information on the resourceid element, see resourceid (DITA 1.3 Specification). To learn how to use resourceId to create peer links, see URL (Peer Links).

Heretto Portal 26.02.19

• Added. Heretto Portal now supports the DITA 1.3 appid and appname attributes on the resourceid element, in addition to the existing id attribute. Either id or appid is required; appname is optional. The resourceid element is now also supported in topicmeta, not just prolog. When multiple topics share the same ID value in the resourceid element (not recommended), portal redirects to the first topic in the sitemap. Requires Heretto Deploy API 26.02.19.

  For more information on the resourceid element, see resourceid (DITA 1.3 Specification). To learn how to use resourceId to create peer links, see URL (Peer Links).