tracker issue : CF-4201686

select a category, or use search below
(searches all categories and all time range)
Title:

cfpdfform with name attribute makes the PDF unsignable in Reader DC

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/Fixed

Reporter/Name(from Bugbase): George Alsobrooks / George Alsobrooks ()

Created: 03/22/2018

Components: Document Management, PDF Form

Versions: 2016,11.0

Failure Type: Incorrectly functioning

Found In Build/Fixed In Build: 11.0.13.303668 but may have existed previously / 2018.0.0.308666

Priority/Frequency: Normal / All users will encounter

Locale/System: English / Win 2012 Server x64

Vote Count: 0

Problem Description:  If cfpdfform with the name attribute is used to populate a PDF object and passed to the user the user will not be able to sign the form in Adobe Acrobat Reader DC (reader not pro).   The PDF loses the extended features that allow reader to sign.

Steps to Reproduce:  The below code gives an example of using cfpdfform with the name attribute to populate the PDF.

<!--- THIS WILL NOT WORK (filesize: 93kb) --->
<cfpdfform action="populate" source="DD2875_2009-08.pdf" name="pdfdata">
    <cfpdfsubform name="topmostSubform">
        <cfpdfformparam name="syst_name"	value="TEST SYSTEM">
        <cfpdfformparam name="location"		value="SOMEWHERE, EARTH">
    </cfpdfsubform>
</cfpdfform>

<cfheader name="Content-Disposition" value="attachment; filename=test.pdf" />
<cfcontent type="application/pdf" variable="#toBinary(pdfdata)#" />

Actual Result:   PDF is generated, but user receives the following message when opening the file in Adobe Acrobat Reader DC   (Reader version not PRO) and cannot sign the PDF.   "This document enabled extended features in Adobe Acrobat Reader.  The document has been changed since it was created and use of extended features is no longer available.  Please contact the author for the original version of this document."

Expected Result:  User should be able to open the PDF without error in Reader and sign the PDF.   ColdFusion should not modify the PDF structure.

Any Workarounds:   The PDF generated by the above code should generate the exact same PDF generated by the code below.   This will generate a PDF that the user can open without error and still sign.   Using a file is a workaround, but shouldn't be required.

<!--- THIS WILL WORK (filesize: 94kb) --->
<cfpdfform action="populate" source="DD2875_2009-08.pdf" destination="test.pdf" overwrite="yes">
    <cfpdfsubform name="topmostSubform">
        <cfpdfformparam name="syst_name"	value="TEST SYSTEM">
        <cfpdfformparam name="location"		value="SOMEWHERE, EARTH">
    </cfpdfsubform>
</cfpdfform>

<cfheader name="Content-Disposition" value="attachment; filename=test.pdf" />
<cfcontent type="application/pdf" file="#ExpandPath('test.pdf')#"/>

Attachments:

  1. March 22, 2018 00:00:00: DD2875_2009-08.pdf

Comments: