The official release documents for 184.108.40.206:
In addition there are a couple of changes in 220.127.116.11 that deserve to be called out here.
The main change brought by RPE 18.104.22.168 is the new PDF Output. We have introduced this as the “New PDF Driver” in RPE 22.214.171.124 but there were performance and consistency issues we could not solve at that date which prevented us from making the driver the default one. For details see this: RPE 126.96.36.199
With 188.8.131.52 the performance of the PDF driver is improved and the consistency issues are fixed. And while the performance and scalability of the new PDF driver are still not on par with those of the legacy one, the quality of the PDF more than compensate in our opinion. See the PDF Output Reference for details.
The old PDF driver is preserved as the legacy PDF output for those scenarios where the size of the generated document cannot be handled by the new PDF. See the Legacy PDF Reference for details on how to enable that output and more.
Back to the new PDF output there are a couple of capabilities that I want to highlight:
- Word and PDF capability gap is reduced – a good number of properties were supported for Word output but not for the Legacy PDF output. With the new PDF output the overlap is much greater and the resulting PDF and Word documents are closer looking
- style sheets – it is now possible to use Word style sheets for PDF output. The style sheets provide style and content to the PDF document
- automatic font detection – it is no longer necessary to specify the font to use for non-Unicode fonts. RPE will determine the most appropriate font to use. Still you have the ability to provide a font name for RPE to use if a certain font is not available on the machine. This
- Include files – the content of included files is now physically embedded in the PDF output while in the legacy PDF output a hyperlink is created for the include. Some supported file formats are: rtf, doc, docx.
- fields – TOCs/TOFs/TOTs etc can have page numbers and in general fields in PDF are much better supported and rendered
Specifying the authentication method
With RPE 184.108.40.206 it is now possible to specify the authentication method to use. The list of supported methods is: basic, form, oauth and oauth1a.
- If left empty RPE will work as it does today by trying to detect the protocol.
- If the authentication method is specified RPE will use it immediately, avoiding the detection mechanism, and this can result in significant performance improvements for those reports that make many requests to data sources that use basic (ReqPro via DataServices, RTC, RQM) or OAuth/OAuth1a ( RRC) authentication.
Rich Text handling
A lot of work has been done to correct and improve how RPE handles rich text coming from data sources such as RRC, RQM and other. Some of them are captured in the APAR fix list.
Corrections to license usage
A RPE license is now consumed for the entire duration of the document generation including the execution of the pre-commands, if any exist.