Feature Request

When the PDF import option does not appear during article creation, the interface gives no indication of why it is unavailable, leaving the user unable to tell whether a configuration change would resolve it or whether it is unavailable for a different reason. Add an inline message or tooltip next to the import options in the Create Article flow and the Import panel that states the specific condition preventing PDF import from appearing (for example, the project’s default editor setting), with a link to the relevant setting where applicable. Benefit: Users can immediately identify and resolve the condition blocking PDF import, or clearly understand it is unavailable for a reason outside their control, without trial and error.

We have an old version that we would like to archive. But what we have noticed is that when we export content, only the last version is exported. Version history is not extracted. Is there any way to ensure that the export includes the article version history?

The current library used for Word Import has limitations. Tables inserted from Google Docs are rendered as table headers and font, background colours are not retained in the table after import

We would like to request a feature that allows users to export the entire project/knowledge base articles into a Microsoft Word (.docx) format.

We would like to request the ability to configure a separate font specifically for the Japanese (JA) PDF template. We have noticed that the current font renders bold text correctly, but commas and certain punctuation marks are displayed incorrectly. We request support for a Mincho (serif) font, preferably Noto Serif JP, for the Japanese PDF template, while keeping the English (EN) PDF template unchanged. This would ensure that both bold text and punctuation are rendered accurately and improve the overall readability of Japanese PDF exports.

Currently, when a project is exported, articles marked as deprecated are included in the offline documentation. While including these articles is the expected behavior, the exported documentation does not indicate that they are deprecated. This can lead to confusion for readers of the offline documentation, as they are unable to distinguish between active and deprecated content. Requested Enhancement: Add a visual indicator or label in the offline documentation export to identify articles that are marked as deprecated in the knowledge base. This would ensure consistency with the online experience and help users easily recognize deprecated content in exported documentation.

Our clients rely on the ability to download our release notes into Excel so they can filter/sort and perform UAT on our released items when they go to their sandbox environment. We previously had this capability with our prior vendor and now because we are unable to allow our clients to download their content from a table into Excel, we are duplicating work by maintaining our release notes in a table AND a separate Excel file, that we also have to ensure are always in sync.

We would like to have an article-level selection in the import and export project feature instead of a category-level selection. It would help us to select the articles that should be included in our exports.

Document360 currently allows exporting articles only as PDF files, while importing requires only .docx files. This breaks the workflow for moving content between Sandbox and Production. Supporting PDF imports, in addition to .docx, would resolve the inconsistency and enable a smoother, bidirectional content migration process.