EEX 9.2: Send Back For Revision Approval Comments At Expense Report Level Containing Quotes And CRLF (Carriage Return, Line Feed) Lines, Get Displayed In HTML Escape Sequence Format (Doc ID 2093736.1)

Last updated on MARCH 16, 2016

Applies to:

PeopleSoft Enterprise FIN Expenses - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.

Symptoms

ISSUE:

The Comments at the View Approver Comments delivered page (EX_COMMENTS_RJCT) for an Expense Report that has been Sent Back For Revision, get displayed with HTML tags should the original Comments entered by the Approver in order to justify the action taken include quotes, or statements mentioned in different lines.

REPLICATION STEPS:

     - Create a brand new Expense Report transaction, and submit it for approval
     - Have the Approver take the action of Send Back For Revision this transaction, by entering the below comments justifying the action taken:

          {Sending back "Test" expense report
          "Modify" and re-submit the report}

     - As the Employee owner of the Expense Report, open the received transaction in Create/Modify mode
     - See how the red highlighted line containing the Send Back For Revision comments contains 'quotes' and 'lines' in HTML tags
     - Click on the comments link to go to the View Approver Comments page (EX_COMMENTS_RJCT)
     - Confirm there as well that the Comment field contains gibberish data, very difficult to read/understand for the user

To gather more information concerning this scenario and its related problem, refer to the available Replication Steps Word Document here linked containing the complete configuration and the replication steps necessary to reproduce the issue.

BUSINESS IMPACT:

The Comments are unreadable for the User, or very user unfriendly to say the list, as the wording is completed with gibberish characters, and gets the information confusing.

EXPECTED BEHAVIOR:

Approver Comments should always be able to get properly displayed, and be readable no matter how it was written.

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms