How does the PDF Converter for SharePoint Online differ from the on-premise product

The PDF Converter for SharePoint Online as well as the on-premise product are both based on the same mature processing engine that handles conversion, merging, watermarking, securing and OCR processing. However, due to limitations in the SharePoint Online platform, and significant architectural differences, both products do not (yet) share the same end-user facilities.

Our aim is to provide full feature parity between the 2 products. Please note that the Online App can also be installed in SharePoint on-premise

Please find below an overview of the similarities as well as the key differences.

 

Similarities

 

Key Differences

  • No direct Nintex Workflow support due to lack of 3rd party integration facilities in Nintex for Office 365.
    As a workaround trigger a SharePoint Designer workflow from Nintex Workflow.
  • No K2 workflow support due to lack of 3rd party integration facilities in that product.
    As a workaround trigger a SharePoint Designer workflow from K2.
  • No API access. (As a workaround trigger a workflow or install the stand-alone Muhimbi PDF Converter Services on an Azure instance.)
  • No (HTML to PDF) conversion of URLs that reside in SharePoint.
    As a workaround merge meta-data into MS-Word or watermark meta-data into templates.
  • No access to the underlying config files to 'tweak' settings.
    As a workaround use our XML syntax to override settings during conversion.
  • Due to the nature of the underlying platforms, both products are licensed completely differently.
  • The SharePoint Online edition is much easier to install, the back-end is monitored and maintained by Muhimbi.

 

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.