The current version of the Word Template Export has some functional restrictions:
No graphic elements, such as emojis, in template language statements text content
Wiki markup rendering does not support Wiki "anchor" links
No nested
...
tables in template language statements text content
Word tables with multiple rows in template language statement text content must be preceded and followed by at least a single space.
Please read Working with Tables to understand rendering restrictions and conditions.Exporting with an active tree filter requires a template that uses the $selectedFilter expression and the filter statement
Use of text boxes may cause errors in word template
Since exporting pages rely on application links, there are some limitations when using the $selectedTreePage expression
Web links added from Issue Links
...
Working with Tables
Word tables in template language must follow certain conditions to render data in a new table or in table rows.
...
Expand | ||
---|---|---|
| ||
|
Expand | ||
---|---|---|
| ||
There are 2 Confluence REST APIs used per page rendered on a Word export. To get page details (created, creator, url, updated), we call /content/{pageId}. To get HTML content, we call /content?...expand=body.export_view. During the first API call per page, values will be "cached" so that succeeding statements that will get page details or content on the same page will just retrieve the cached value to avoid duplicate connections to Confluence REST API. If there is a problem with connecting to the linked Confluence API URL, timeout is set to 500 ms or 0.5 sec (per API) before an empty string during export. Assuming details and content will be retrieved, failed connections will add 1 sec per page to the Word export performance. With this, we advise to make sure application links and permissions are configured correctly to avoid performance issues. |