Generating Output Documents on ServiceMax Go
Output Documents generated on Salesforce via the browser use the Salesforce PDF engine, which is a proprietary PDF generation engine. Output Document templates designed to utilize features specific to the Salesforce PDF engine are not necessarily compatible with modern browser functionality that exists on mobile devices.
Go for Android and iOS
Output Documents generated locally on iOS and Android devices use the native browser of the mobile device to convert the HTML template to PDF. The specific rendering is a result of the native browser’s capabilities, Safari for iOS and Chrome for Android.
The Go app does not determine the styling or layout of the PDF output result. Output Document templates that are designed to produce specific results using the Salesforce PDF engine do not necessarily produce the same results when generated locally on mobile devices using ServiceMax Go. Formatting/styling differences such as font size, table formatting, etc, that may be observed when generating output documents locally must be resolved by updating the document template’s HTML and CSS so that it is compatible with modern browsers. Some CSS styling properties that affect Salesforce-generated PDF files may not have a mobile-friendly equivalent.
Known Limitations for Output Document PDF Files Generated on Mobile Devices
• The Safari browser does not support the CSS @page rule, so @page cannot be used for defining page numbers, page margins, etc.
• The Chrome browser does support some properties of the CSS @page rule but does not support all properties. For instance, @page properties can be used to define page margins, but cannot be used to define page numbers.
• Neither the Safari nor Chrome mobile browsers support repeating headers or footers in output document PDF generation.
Generating Output Documents on the Server from a Mobile Device
Go (Android & iOS) does support an option to use the Salesforce server PDF engine to generate output documents. For documentation of this feature, see Enabling Output Document Generation on Server.
When the option is enabled, an HTML preview version of the output document will be displayed on the device initially. When the Finalize button is used to complete the document, the document is sent to the server and the final PDF is created on the server and synced back to the device. An active internet connection is required to generate the output document on the server.
A fallback option is introduced for scenarios where the Server Generation option is enabled, but the technician does not have online connectivity.
For such a scenario, the technician has the option to use the local device PDF generation to generate the final document without having to establish an online connection. With this option, the technician is declining server generation for a particular output document, and the locally generated PDF is the final version. The styling of documents generated locally on the device may differ from those generated on the server.
 |
• Special handling is added to the Go app to support defining page margins and page numbers on output documents generated locally on the mobile device. For more information, see Configure Page Numbers and Margins.
• The value returned on the picklist fields is based on the configuration in the template designer:
◦ Using the Insert Label option returns the display value of the picklist field.
◦ Using the Insert Value option returns the API value of the picklist field.
◦ Using neither the Insert Value nor the Insert Label option without any operator returns the API value of the picklist.For more information, refer to the Template Designer section.
|