Carlo, I did get this resolved. The problem was related to my assigning a value to elementName, as you suspected.
myAnnot.elementName = 'ilr-approve';
In comparing the xfdf between programmatically added annotations vs webViewer UI added annotations, I noticed that the annotations I added, despite appearing in the tag , were not being being included in the downloadPDF() call. See xfdf snippet below:
<annots>
<ilr-approve ... > // elementName that I added
<contents>My added Content</contents>
</ilr-approve>
<freetext ...> // elementName webViewer UI added
<contents> My added Content </contents>
</freetext>
</annots>
A few other things:
- I didn’t need to use set/getCustomData in the setContents call.
- I did use setCustomData though in place of elementName as you suggested to help me name my annotations
- I would never have thought that using the elementName property would have caused this, I’m not really sure of it’s purpose.
- Also, I would have assumed that any annotations included in the annots section of the xfdf would have been merged into the downloaded PDF.
Thanks for your help with this.
Dave