Riffat Wyne
Our customers, technical services and internal SSU really want to have "Published/updated status, date and version number" displayed under title or under main heading and in the footer "article/category name with version number" of the PDF export. This is becoming a critical issue for us not only for external but also for our QA processes. The exported PDF's are being distributed and circulating without the controlled metadata and it is becoming a very huge challenge.
D
D360 Product Management
Merged in a post:
Non TOC internal linking unavailable in PDF exports
U
Usama Ansari
We want exported PDFs for articles with different subheadings or sections to be linked when clicked.
The TOC linking within the export works fine. For example, if a TOC has an H2 that says "Tech Writing", clicking on it, the page jumps to that heading.
Outside of the TOC, for example, if the topic contains internal linking to the following headings:
- Best practices of Tech Writing
- Word Usage guide in Tech Writing
- How do you benefit from Tech Writing?
The links don't jump to that heading. Instead it opens externally, as in a browser (see image).
We want the PDF exports to jump to the headings that are linked internally and not just TOC links. For links that are external, such as to a different article or another webpage, the behavior makes sense.
K
Kavya
Hi Usama Ansari
Thank you for bringing this up and for the clear explanation — that’s a very valid observation.
Merging this request with the existing PDF Export Enhancement thread.
This enhancement is already planned for release this quarter. As part of the update, internal links within exported PDFs — including those pointing to subheadings or sections in the same export — will correctly navigate to the respective section within the PDF instead of opening externally.
For links that point to other articles or external pages not included in the same export, the current behavior (opening externally) will remain unchanged.
R
Rana Owais
Our own internal teams have echoed the same frustration. If our staff struggle to gather sets of docs, we can only imagine how frustrating it must be for customers who don’t know the system as well.
Z
Zain Naqvi
Other platforms already provide this type of grouped download, and customers are quick to notice the gap. It reflects poorly when we fall behind on such a straightforward usability feature.
M
Mashhud Ali
This feature directly impacts adoption. When customers feel friction at the basic document access level, it undermines their overall trust in the portal as a reliable resource hub.
m
mehak saeed
Customers using the portal for research or training are particularly vocal about this. They need complete sets of materials and don’t understand why the portal forces them into repetitive downloads.
S
Sidra Saleem
Lack of bulk PDF download makes sharing internally harder too. Teams often want to circulate a set of docs, but without this feature, they resort to stitching together files manually.
n
nouman wali
As our content grows, this pain point will only get worse. The PDF download feature should not be limited to the article level. It’s important to make this feature scalable, rather than expecting customers to handle dozens of manual downloads.
A
Aamna Kamran
From a product perspective, this is a low-bar capability. It should not require extensive effort from users just to accomplish something as simple as gathering related documents together.
Load More
→