This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision |
| kb:kb_articles:kb1087 [2024/01/30 18:51] – bshumsky | kb:kb_articles:kb1087 [2024/01/30 18:54] (current) – bshumsky |
|---|
| There have been reports on some systems that PDF generation in OIPI "Classic"(VSPRINTER/VSPRINTER1) often fails to generate valid, or complete, PDFoutput. This has been confirmed to be an issue, but unfortunately it has not been resolved for this release. | There have been reports on some systems that PDF generation in OIPI "Classic"(VSPRINTER/VSPRINTER1) often fails to generate valid, or complete, PDFoutput. This has been confirmed to be an issue, but unfortunately it has not been resolved for this release. |
| |
| As a workaround, OIPI "Classic" in OpenInsight 10.0.8 now supports an alternate method for PDF generation. In the configuration record (found in the SYSENV table, and named either CFG_OIPI*<appid>*<username>,CFG_OIPI%%**%%<username>, CFG_OIPI*<appid>, or simply CFG_OIPI), field 3 can now specify the name of a "Print to PDF"printer. On Windows 10 systems, for example, there is an included "Microsoft Print to PDF" printer, though other options (both free and paid) exist with similar or advanced capabilities. | As a workaround, OIPI "Classic" in OpenInsight 10.0.8 now supports an alternate method for PDF generation. In the configuration record (found in the SYSENV table, and named either CFG_OIPI*<appid>*<username>,CFG_OIPI%%**%%<username>, CFG_OIPI*<appid>, or simply CFG_OIPI), field 3 can now specify the name of a "Print to PDF" printer. On Windows 10 systems, for example, there is an included "Microsoft Print to PDF" printer, though other options (both free and paid) exist with similar or advanced capabilities. |
| |
| |
| |
| {{kb1087_1.jpg}}I | {{kb1087_1.jpg}} |
| |
| |