Using the PDF Converter

The PDF Converter is available for use when the Save as PDF control is not present on a view or form or the designer don't want to use the Save as PDF control. The Broker also allows added functionality as you can specify dynamic URL’s and HTML and you are not limited to taking a snapshot of what is currently reflected on the screen. A snapshot can be taken for example of http://www.google.com.

When using the PDF Converter, the following should be considered:

  • Authorization inheritance will be broken by default on the SmartObject in order to prevent unauthorized use of this SmartObject in solutions. Security Administrators can grant view permissions on the SmartObject to specific users that are aware of the risks of using it in their solutions.

  • Since the PDF Converter relies heavily on manual input, the outcome can not be controlled and debugging might be required if the behavior does not conform to the intended use. It is important to ensure the correctness of what is captured before continuing with the process.
  • It is highly recommended to rather use the Save as PDF control as all of the above is built into the logic behind the control.
  • It is important to use a valid SSL certificate in environments with an HTTPS URL. If the certificate is invalid or self-signed, the PDF may fail to convert the view or form, CSS style files may not be included, and images may not render in the PDF.
  • Other scenarios where the PDF converter may fail are when there are various security restrictions on the computer or network, like the firewall blocking access to the Certificate Revocation List.
  • See PDF Converter Server-Side Request Forgery Prevention Configuration for information about security settings you can configure to restrict which hosts and IP addresses it is allowed to load any type of resource from.
See the following resources for more information: