Excel currently does not, but the setting defaults to TRUE. Word and PowerPoint offer object model arguments that allow the add-in to request keeping IRM settings for PDFs via the ExportAsFixedFormat family of functions. At the appropriate time, we’ll re-enable honoring the request, resulting in potential encrypted PDFs. We’ve disabled all requests via the object model to keep encryption for PDFs. Transition periodĪs the Export to PDF feature launches, we’re introducing a temporary mitigation to allow you time to update your add-ins. Note that add-ins that provide a custom IMsoDocExporter instance don’t use Office’s PDF encryption logic and therefore shouldn’t need to mitigate anything - you’ll need to do your own PDF encryption, if desired. Your add-in may either fail or fail to produce meaningful results if it does any post-processing without knowing how to decrypt the PDF. If the source document is encrypted, the output PDF will also be encrypted with Microsoft IRM protection for PDFs. Potential challenges to existing VBA add-insįor add-ins that use an object model path such as the Document.ExportAsFixedFormat2 method to ask Office to export to PDF, if the add-in doesn’t provide a custom IMsoDocExporter instance via the FixedFormatExtClassPtr argument, then the add-in will inherit Office’s PDF code. This applies to VBA for Word, PowerPoint, Excel. This feature may cause some add-ins to fail and may require development effort to adjust to new Office behavior. Office also enables Office Add-in developers to hook into and reuse some or all of Office’s PDF creation code. Office is shipping a new feature that enables PDFs created from Office using Export to PDF or Save As PDF to retain the source document’s labels or encryption into the output PDF.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |