Utilizes Apryse Webviewer API (Version 10.1.0)

See connected demo module for example usage

To Implement:

1. Reference the Apryse Module's PDFViewer Web Block in your application
2. Pass in a PDF Binary or URL and also a filename
3. Handle the SaveDocument event by pushing the output binary into your file storage solution

PDFTron API Methods Implemented So Far:

Load Document From Blob or URL

Export Annotations as Blob, then convert to Base64 to pass into OutSystems

**Important Notes**

• The Apryse Integration relies on specific mime-types in order to render
• By default, those mime-types aren't handled on an OutSystems webserver
• To get around this, there are three options depending on your environment type:

OutSystems Personal Environments:

• Since you don't have access to modify mime-types on Personal environments at this time, the default configuration of this module is utilizing a public CDN and accessing only the mime-type exceptions via a worker. 
• See OnRender JS inside of PDFViewer WebBlock for more info 
• The public CDN was provided by Apryse and is for development purposes only. There is no uptime or availability guarantee.

OutSystems Self Managed Environments:

• Edit your web.config file directly on your webserver to modify or add mime-types or follow directions below for Cloud Hosted Environments
• Then you can comment out or delete the default CDN resource paths inside of the OnRender JS of the PDF Webviewer Web Block- meaning all resources will be loaded locally

OutSystems Cloud Hosted Environments:

• Use the factory configuration forge component to modify or add mime-types
• Then you can comment out or delete the default CDN resource paths inside of the OnRender JS of the PDF Webviewer Web Block- meaning all resources will be loaded locally

**Apryse trial usage allows unlimited usage in development otherwise see pricing info here

**If you need additional support from Apryse, please contact Apryse Support here