Feature Request

When importing Word documents generated from Google Docs entire table is rendered as table headers and they are in bold formatting. It would be great to have the table in a normal paragraph formatting.

Improve the Word import behavior to preserve ordered list numbering when lists are interrupted by images or headings. Currently, due to a limitation in the Mammoth Word import plugin, ordered lists that appear between headings or are interrupted by images may not retain their original numbering during import. The enhancement would ensure that hierarchical list numbering from Word documents is preserved correctly during the conversion to HTML.

When importing a word document as an article, the ordered list gets converted to an unordered list.

When importing a Word document into the Advanced WYSIWYG editor, certain formatting elements are not preserved correctly. Current Issues: Auto-numbered sections in the Word document are removed during the import process. Double-column lists are not rendered properly after the import.

In private-hosted Document360 projects, importing certain Word documents can fail with errors such as “Operation Failed” or “Something went wrong, please try again later”, even when the same document imports successfully in SaaS environments or older platform versions. Analysis showed that in some cases, the Word import process takes longer than expected in private-hosted environments, leading to request timeouts (for example, 504 Gateway Timeout) before the import completes. This causes the import to fail or remain stuck in an “In progress” state. Although an immediate mitigation has been applied to allow more processing time and unblock imports, Improving the robustness of the Word import mechanism, especially for private hosting, would help prevent timeouts, improve reliability, and ensure consistent behavior across environments.

It's inconvenient to have only a 15MG limit when I import a Word Doc in IMPORT/EXPORT --> IMPORT ARTICLES. Please increase this limit. It's 2023, 15MG is NOT that large. :) Thanks.

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

When a PDF file is uploaded to Drive, and its link is inserted into an article, exporting the article to PDF preserves the link correctly. Clicking the link opens the file as expected. However, the generated URL includes a SAS token (Shared Access Signature). Once the SAS token expires, users receive an AuthenticationFailed error when accessing the file. Currently, the SAS token remains valid for approximately 8 hours, after which the link breaks. Expectation - The nested PDF file should be active at all times

At times, the export failure status does not update in the UI for large content. After triggering the PDF export, the status is in progress, but after the background job completion, the success/failure status is not appended. While regenerating the same template, the status is updated with a success or failure status.