FAQ


Please find below answers to the most frequently asked questions. More details can be found in our comprehensive Knowledge Base. A separate FAQ for the real-time watermarking and secure OnOpen facility is available as well.

If your question is not covered below then feel free to contact our friendly support desk.

Installing the App is very straightforward. It is a matter of searching the SharePoint App store for Muhimbi and selecting the option to deploy the App to your site collection. Having said that, some organisations tightly control which Apps may be installed via SharePoint's App Catalog, in which case you will need to contact the team that looks after your SharePoint environment. Details can be found in this Knowledge Base Article.

Please note that due to technical limitations in SharePoint's App Model, the workflow actions must be installed separately.

If you only wish to use our Software from Microsoft Flow then there is nothing to install. Just pick 'Muhimbi PDF' from Flow's list of standard services.

Although our SharePoint user interface is powerful yet easy to use, the PDF Converter really shines when used from automated workflows. An overview of the available workflow actions can be found in this Knowledge Base article.

Please note that due to technical limitations in SharePoint's App Model, the workflow actions must be installed separately.

If you wish to use Muhimbi's Workflow Actions from Microsoft Flow then that is possible as well. For details see this Knowledge Base article.

It is pretty easy to automate an operation, but you need to have a basic understanding about how to create a workflow using the free SharePoint Designer tool. For a real world example see this video.

Microsoft Flow tutorials can be found in this Knowledge Base article.

Each subscription level comes with a different Maximum Operation Size and Operations Per Month allowance. The maximum size decides the size, in bytes, for a single operation, this includes the total size of all source files in a single merge operation as well as the size of a single conversion.

The number of operations per month are the number of individual operations carried out. Examples of a single operation are: converting a file, watermarking a file, securing a file, carrying out OCR on a single document etc.

Each subscription level comes with a different Operations Per Month allowance (see previous point above). When a subscription has reached 75% of the allowance you will receive an automated email requesting you to contact the Muhimbi team to make arrangements. When reaching 100% of the allowance, without making any arrangements, the software will cease to work for the remainder of the month.

If 75% is not the correct trigger for your organisation then please contact our support desk to change this figure.

Yes you can, providing you use the most recent (9.8) App and Workflow actions. For details see this blog post.

Being able to convert SharePoint pages (HTML) to PDF is a popular feature used by many of our on-premise (SP2007-SP2016) customers. In the current SharePoint Online release it is possible to convert all kind of HTML content to PDF, just not URLs to resources that require SharePoint Online authentication. We are working on it and expect to deliver support for this in a follow up release.

If you would like to integrate with the Muhimbi PDF Converter for SharePoint Online from your own App or code then you have the following options:

  1. Use our REST based API from C#, Java, JavaScript, PHP, Python and other languages.
  2. Create SharePoint Designer workflows and invoke these from your own code.
  3. Create Visual Studio Workflows and invoke these from your own code. Contact us for sample code.
  4. Use our Microsoft Flow Actions and invoke it from your own code or service.
  5. Use our PDF Converter Services product and install it on your own Azure / Amazon hosted server. This product comes with a comprehensive and well documented API. Please keep in mind that unless you are creating an App for internal use you most likely need a separate OEM / SaaS license.

The on-premise version of the PDF Converter for SharePoint has supported Nintex Workflow for years and K2 as of version 7.3. Our plan is to integrate with the Online versions of both products, but that will be part of a future release as at the time of writing Nintex Workflow Online does not support third party workflow actions. Until then you can create a SharePoint Online workflow using SharePoint Designer and trigger that workflow from K2 or Nintex Online.

Muhimbi's customer base spans all industries, organisational sizes and geographical locations. Different industries and countries have different rules and regulations, for each industry that has no reservations about documents being processed in a secure manner by an automated third party system, there is any industry that does not allow documents to be accessed by third party systems at all, period! No matter how secure the underlying technology is.

The Muhimbi PDF Converter is a very flexible App that allows customers to use their own servers, if strictly needed, place certain customers on private servers and even control the geographic region your documents are processed in. For more details see this Knowledge Base Article.

Most documentation can be found in our Knowledge Base. If you prefer to read a PDF based version then you may want to have a look at the User Guide that comes with the On-premise version of the PDF Converter. The SharePoint Online version of the product works largely the same, although certain chapters about integration with Nintex and K2 do not apply.

Sample code for C#, Java, Python, PHP, JavaScript and other languages can be found in our GitHub repository.

As always, if you cannot find the answer, or if you have any questions, then feel free to talk to our friendly support desk. This is not just your average 'run by monkeys' support desk, these are knowledgeable people who know what they are doing and are quick to reply.

The on-premise version of the PDF Converter for SharePoint can convert files to any location within a single Web Application, including different site collections, as described here. Unfortunately SharePoint Apps distributed via Microsoft's SharePoint App Store are much more restricted and can only convert files to locations in the current site collection (including sub sites). For details see this blog post (please pay particular attention to the section in bold red, remember to use a trailing slash when targeting folders without specifying a file name and to never start a path with http:// or the host name..).

If you wish to write converted files to a different site collection then you will need to carry out some manual development work or use our Microsoft Flow actions as described in this Blog Post.

Ever since Muhimbi was founded in 2008, our aim has always been to support all current and future SharePoint versions. SharePoint versions 2007 to 2016 largely share the same architecture resulting in mainly small tweaks (and some not so small ones) to make the same product work on all SharePoint versions. To us, on-premise means a SharePoint 2007-2016 installation that you have installed yourself or someone (other than Microsoft) is maintaining on your behalf.

Over the last few years Microsoft has been pushing 'The Cloud', popularising a product that is known as SharePoint Online, or Office 365. Depending on who you talk to these terms are used interchangeably, but we call it SharePoint Online. Although the SharePoint Online user interface resembles SharePoint 2013, under the hood it is quite a different beast, especially where it comes to 3rd party extensibility. Our core conversion service is largely the same, but the entire front end (SharePoint User Interface, Workflow Actions) has had to be redeveloped from scratch.

As a result, and due to limitations of the SharePoint Online platform, some of the features provided by the on-premise version of our software are not yet available in the Online version. We continue to work on it as we aim for feature parity between both versions. For an overview of the key similarities as well as the key differences see this Knowledge Base article.