E-BI/XMLP: Using Rich Text Enabled (RTE) Fields In BIP Reports After Upgrade To PeopleTools 8.53 PeopleSoft 9.2
(Doc ID 1636124.1)
Last updated on JANUARY 12, 2023
Applies to:PeopleSoft Enterprise PT PeopleTools - Version 8.52 and later
PeopleSoft Enterprise HCM ePerformance - Version 9.2 and later
Information in this document applies to any platform.
This document applies to any 9.2 Application release.
Starting in PeopleTools 8.52, BI Publisher reports are fully capable of displaying RTE field data in a BIP report. This is documented in the BIP PeopleBooks, under the section "Understanding Rich Text Editor Data in BI Reporting".
As per the PeopleBooks documentation for PeopleTools 8.52 and 8.53, specific measures need to be in place in order to successfully display the RTE field data in a BIP report:
- (XML File DataSource only): If the XML file is produced using XMLDoc or File Layout, then the conversion of data to XML results in the conversion of reserved XML characters to their entity-reference form (for eg. “<b>Bolded text...” becomes “<b&rt;Bolded text…”). This invalidates the XHTML tags in RTE data and so will need to be restored using the PeopleCode substitution logic provided in PeopleBooks.
Limitations with the 8.52 Implementation:
1) An Application upgrade (eg. HCM 9.1 to 9.2) resulting in a mix of RTE (Rich Text Enabled) and non-RTE data in the same Long Character field, can cause XML parser errors:
If a field that was previously non-RTE, is made to be an RTE field after an Application upgrade, this can result in the field containing both plain text (pre-upgrade entered data) and rich text (post-upgrade entered data). BIP reports using this RTE field can potentially error out with XML parser errors. More specifically, it’s the PeopleCode substitution logic applied for XML File-based datasources, and intended to handle only rich text data, that can lead to these report errors. The substitution logic is meant to un-escape XHTML tags in RTE data (eg. “<b&rt;Bolded text…” ó “<b>Bolded text…”), but can end up un-escaping legitimately escaped reserved characters in non-RTE data (eg. “A&B in Plain text…” ó “A&B in Plain text…”). The presence of these un-escaped reserved characters in the XML data (post-substitution) will then cause the BIP Report engine to error with xml (SAX) parser errors.
2) Special characters in RTE fields will cause XML parser errors:
Use of the delivered configuration file PT_RTE_CFG_PTXP for the Rich Text-enabled Long Edit box, will hide the Special Characters button in the Rich Text editor toolbar. However, special characters such as the Pound Sterling currency character (£), or accented characters (é), can still be inserted directly into the Rich Text editor via keyboard entry (depending on the keyboard language in use). These special characters are represented in the rich text data using html named entities (£, é, etc.). The xml parser cannot recognize these characters as it has not been supplied with an XHTML DTD identifying them as 'standard' named entities
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
Goal Solution Moving from the 8.52 solution to the new ‘built-in’ RTE solution in 8.53 My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.