E-BI/HCM: BI Publisher Report HTML2FO Function Doesn't Support Hex Unicode Code-points
(Doc ID 2019753.1)
Last updated on NOVEMBER 27, 2019
Applies to:PeopleSoft Enterprise HCM ePerformance - Version 9.2 to 9.2 [Release 9]
PeopleSoft Enterprise PT PeopleTools - Version 8.4 and later
Information in this document applies to any platform.
Special formatting codes are often found in the text data drawn into BI Publisher reports. Examples include the ePerformance Document.
PeopleTools version: 8.53
Platform: Microsoft Windows x64 (64-bit)
Platform version: 2008 R2
Database: Oracle Database - Enterprise Edition
Database version: 18.104.22.168
Database Platform: Microsoft Windows x64 (64-bit)
Database Platform Version: 2008 R2
When attempting to create a new performance document and entering the Hex Unicode code-points, the function HTML2FO does not convert correctly the code-point in the output report (e.g. code-point ’ should be translated as a right single quotation mark, ( ’ ) in the output report),
The Unicode code-points appear correctly in the PIA prior to printing.
The issue can be reproduced at will with the following steps:
1. Login to PIA
2. Navigate to Manager Self Service -> Performance Management ->My Performance Documents -> Create Documents
3. Create a performance document.
4. Progress the appraisal process to mid-year review.
5. In the Manager's comments, enter text into the Manager Comments field for Mid-Year Discussion.
6. Save the changes.
7. Run the following SQL Statements:
SET = '&var'
WHERE EP_APPRAISAL_ID = ;
8. When prompted for the value of &var, enter the text (without quotes) "’".
9. Navigate to Manager Self Service -> Performance Management ->My Performance Documents -> Current Documents
10. Select the document you created.
11. Click the Print button appearing at the top right.
12. Compare the PIA against the generated report; the generated report will show the literal code-point, the PIA will show the HTML translation.
For example, code-point ’ indicates a right single quotation mark, ( ’ ), and should be translated to such on the report.
Due to this issue, users cannot progress the appraisal process to mid-year review with correct formatting, which impacts business practices.
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