Be sure to test your server PDF generation scripts when migrating FMS to a different operating system. Some fonts–and some characters–may fail to render on one or more operating systems. If your output doesn’t look right, check if the required fonts are installed on the server.
This may be true in version 16 or earlier, but I can confirm that this is not the case in version 17, 18, or 19. Some resources online claim that the account requires fmapp extended privilege in order to run PSOS. You can then transfer the result to a field using Set Field without having the layout dependency.
When the result of Insert from URL is binary data, you must include the cURL option -FM-return-container-variable. My preference is always to save the result of Insert from URL into a variable, since saving to a field requires that the field be on the current layout. The calculation in the example above should work on Linux, Mac & Windows servers. Insert from URL uses a different format for the file path. Insert File is not supported on server scripts so to get the PDF into a container, you need to use Insert From URL. Save the PDF to the temporary folder has important benefits: 1) a new temporary folder is created for every session so there is no risk your data will be exposed to another session running at the same time, 2) the data is destroyed automatically when the session ends. Also check your OnFirstWindowOpen script to ensure any unnecessary steps are bypassed when running on the server.
Set Field Ĭommit Records/Requests Įnsure that With Dialog is Off on the Save Records as PDF script step.Īllow Printing must be enabled in the privilege set, otherwise you will get error 3.Īll of the regular gotchas of PSOS apply, so you need to pass in whatever information is needed to establish the correct context.
0 kommentar(er)
