Visualforce PDF Rendering Considerations and Limitations
OR
RenderasPDF considerations in visualforce
Limitations of the Visualforce PDF rendering service include:
OR
RenderasPDF considerations in visualforce
Limitations of the Visualforce PDF rendering service include:
- PDF is the only supported rendering service.
- Rendering a Visualforce page as a PDF is intended for pages designed and optimized for print.
- Standard components that aren’t easily formatted for print, or form elements like inputs, buttons, or any component that requires JavaScript to be formatted, shouldn’t be used. This includes, but isn’t limited to, any component that requires a form element.
- PDF rendering doesn’t support JavaScript-rendered content.
- Font used on the page must be available on the Visualforce PDF rendering service. Web fonts aren’t supported.
- If the PDF fails to display all of the page’s text, particularly multi-byte characters such as Japanese or accented international characters, adjust the fonts in your CSS to use a font that supports them. For example:
- Arial Unicode MS” is currently the only font supported for extended character sets that include multi-byte characters.
- If you use inline CSS styles, you must set the API version to 28.0 or greater, set <apex:page applyBodyTag="false">, and add static, valid<head> and <body> tags to your page, as in the example above.
- The maximum response size when creating a PDF must be below 15 MB before being rendered as a PDF. This is the standard limit for all Visualforcerequests.
- The maximum file size for a generated PDF is 60 MB.
- The maximum total size of all images included in a generated PDF is 30 MB.
- PDF rendering doesn’t support images encoded in the data: URI scheme format.
- Note that the following components do not support double-byte fonts when rendered as a PDF:
- <apex:pageBlock>
- <apex:sectionHeader
These components aren’t recommended for use in pages rendered as a PDF.
No comments:
Post a Comment