We have fixed an edge case related to the code block element and branching. If your codeblock contained a square bracket [] and you tried merging the file containing that codeblock into a different branch, the codeblock was interpreted as malformed XML. Currently, when your codeblock contains one or multiple square brackets, it is correctly recognized as valid XML and the merging operation completes as expected. That is also true when you add parentheses (), curly brackets {}, or angle brackets <> to a codeblock then branch-merge or branch-replace.

We modified the default behavior of skipping files in a branch-merge operation.

Previously, if you skipped files when branch-merging, for example, because they were irrelevant or still needed to wait for approval, made no changes to the files, and tried merging them again, the files wouldn't be listed because no changes were made to those files since that last branch-merging operation (when you skipped them).

Currently, when you skip files in a branch-merge operation, make no changes to the files, then try to branch-merge the same set of files, all files you skipped in the last operation are listed because there are differences in content between branches.

Both of these behaviors can be the desired default behavior, depending on your preference. The new default behavior is more common which is why we made the change.

We can now restrict the list of note types to only include the ones you need. This configuration requires professional services work. For details, contact your Customer Success Manager.

We have introduced further enhancements to our Image Map editor! You're now able to easily edit attribute values of Image Map links in the Attributes tab without having to open the Source Editor.

We have made a subtle yet valuable improvement to the Suggesting mode. Suggestions to delete elements now show the names of elements in the suggestion cards, which makes such suggestions much easier to read!

We have changed the default element in the drop-down menu when moving chapters in a bookmap. In the past, when dragging and dropping chapter elements on other chapters, the default option was topicsetref which is s rarely used. The new default element is topicref.

When you content-reference (conref) an element that contains an annotated image or figure element, the image or figure is rendered correctly in the Content Editor. For example, when you conref a step element that contains an annotated figure element, the figure shows both the image and annotation.

When you create folders, spaces in your folder names are now automatically converted to underscores (_).

We have fixed a short lived behavior where when creating a DITAVAL, you needed to add the .ditaval file extension manually. Now, the file extension is there for you again!

The Modified column in the Content Library now always contains the year, for example, Tue, March 21, '23. Previously, it showed the year for past years. For the current year, it only showed the day and month.

We fixed an edge case where when you use Adobe Illustrator to convert PDF images to SVG files, then upload them into Heretto CCMS, some information specific to and required by Adobe Illustrator would get stripped from the file making it invalid for Adobe Illustrator. This is no longer the case. After downloading such files from Heretto CCMS, they can be edited in Adobe Illustrator with no issue.

We have added support for Oxygen XML Editor 25. For details, search our help site for Oxygen integration. A list of supported Oxygen products is listed in a linked GitHub account along with necessary plugins.

We have improved the layout and styling of the Links tab in the Resource Drawer. The new styling is simpler, roomier, and easier to follow.

When you edit a localized topic in the Source Editor, the DITA class attributes in that topic, for example, class="- topic/title " or class="- topic/xref ", are no longer lost. This issue was not present when you edited a localized topic in the Content Editor.

We have fixed an issue where modifying a locale (target language) for a file would affect the locale of a version of that file previously saved in a release. The current behavior is:

• When a file and its version saved in a release are identical, they share the same locale. When you modify the locale, the updates are shared between both versions of the file.

• When you modify the file so that it's no longer the same as its version saved in the release, then modify the locale of that file, a new locale for that file is created and your edits are saved in the new locale file. The locale of the file saved in the release remains unchanged.

We have updated the default behavior of our preflight check. Now, preflight check starts automatically when the Publish window opens. Thanks to that you are automatically informed about issues in you publication, if any. This behavior is configurable and the options remain the same: mandatory, automatic (default), manual, or disable. We recommend keeping the default option.

Contact your Customer Success Manager if you would like to make a change to your preflight configuration.

The PDF Generator now supports the toc="no" attribute. As a result, topicref elements marked with toc="no" are excluded from the table of contents (TOC) but the topic content is present in the publication.

You can again preview the styling in a PDF Generator scenario from the Administration interface!

When you publish a deliverable with DITA Open Toolkit (DITA-OT) Cloud to multiple locales (target languages) in one publishing job, all locales get published as expected.

We improved the notification that you see when you try to add a new user and you have already reached the user limit. The notification now informs you exactly why you can't add new users by saying: Error: Limit of available active author accounts was reached.

When adding a new user or viewing the details of an existing user in a short or narrow window, you can now see the full list of password requirements.