...

 v10.1 uses an enhanced technology to generate your form/workflow PDF Snapshots. You will not see any difference in the design-time or run-time user interface - it will be totally seamless! , but your PDF snapshot output may be slightly different (better, we hope!) Behind the scenes,  uses Chromium browser as a rendering engine to generate a snapshot. Since the browser supports all the latest HTML + CSS standards, the snapshot output will match the HTML view of a form/workflow. This has several benefits.

• Workflows will now combine form PDFs and then apply page numbers, so you will have a consistent page numbers count throughout the workflow PDF Snapshot.

• Better support for the CSS page break classes, especially for controls like Textarea and Message that can contain a lot of white space and line breaks in the control content.

• New CSS Classes:
  

  • New f-break-children-avoid CSS class which when applied to a group control, will avoid a page break inside child controls.

  • New f-break-inside-avoid CSS class to avoid a page break inside a specific control.

  • The f-page-break-inside-avoid CSS class is now deprecated but continue to work if already set.

• Improved alignment and consistent printing of all control types
• Improved multi-language print support for Arabic and other RTL languages.
• Supports future  enhancements

...

This enhancements in this release do not require changes to your existing installation setup, forms or workflows. However, there are some changes you need to be aware of regarding the new PDF Generator.

• On Premise Customers please note the additional Upgrade Guide step of ensuring Chrome is installed on the same server as your  installation in order to use the new PDF Snapshot Generator.
• PDF Snapshots generated after the upgrade may look different, depending on the CSS classes you are using and how your Print Styles are configured. We recommend testing your PDF snapshots to be sure they look the way you expect.
  • If you use CSS classes for page breaks in your PDF, your existing CSS classes should continue to work. However, because CSS classes are more consistently supported with our new technology, we suggest that you test and adjust as needed. If you were using the CSS class f-page-break-inside-avoid, we recommend changing to one of the supported page break CSS Classes.
  • If you use the Print header/footer template FREVVO.PRINT_PAGE_COUNT, this will now show the total page count of the workflow (including all forms). It will not give a separate page count for each form in a workflow with multiple forms as it did in past versions.
  • Section controls will now print in the same width as other 12-column controls.
  • Images uploaded in Message controls using the Rich Text Editor will now be printed.

...