Docs Files: PDF issues pin system is page-based and should be file-based

[patrick.chehwan]

This workflow is based on one of our clients using Docs & Issues:

The company receives a PDF file containing the sheets, and those sheets have page numbers based on the number of pages in the PDF (1, 2, 3, etc.). In the example below, notice that A6 is page number 5:

In Docs (Files), they are extracting this PDF into separate pages, which successfully extracts the sheet number as the new separate PDF file name (A1, A2, etc.):

They are reviewing, creating issues and markups on these extracted pages to share with the architects/engineers. In the same example, I created issues on the extracted A6 sheet which has page number 5:

The architects/engineers then sends them a new set of drawings in a PDF file, which could only contain the modified sheets (i.e. the number of pages the PDF has is different). I deleted some pages (between A2-A5) from the main PDF as an example, and kept A6, which now has a new page number (2):

When the client extracts this new set into separate pages, the system would still do the file versioning for them on the sheets that were modified into V2:

However, the page number within that sheet seems to be causing the problem, and the issue pins are disappearing. Notice how the issue pins disappeared from A6 file V2 because the page number is different now (2) instead of (5), although the issues are still there (but not the pins):

Autodesk Docs’ current PDF pin system is page-based, not file-based, and the request would be to have it similar to Build Sheets, where pins are bound to the published sheet.