SR-132123 · Issue 202411
Auto-resize parameters added to Pega Image Viewer
Resolved in Pega Version 7.1.8
When a large TIFF image (over 2,000 x2,000 pixels in size) was loaded into the Pega Image Viewer control embedded into any section, both horizontal and vertical scroll bars appeared and the Fit-To-Width button of the control needed to be clicked to scale down the image enough to eliminate the scroll bars. In order to smooth image display, the system now provides image size initialization during startup using a parameter 'ImageSize' in the HTML which accepts three strings: Normal, BestFit, or FitWidth.
SR-132507 · Issue 201175
Upgraded Apache Commons FileUpload
Resolved in Pega Version 7.1.8
In order to enhance system security, Apache commons-fileupload-1.2 has been upgraded to commons-fileupload-1.3.1.
SR-132588 · Issue 202025
Corrected Save Rule-Connect-JMS with Global Resource Set
Resolved in Pega Version 7.1.8
Attempting to save Rule-Connect-JMS containing dynamic settings to avoid hardcoded parameter values was failing. This was due to a validation step that wrongly converted formatting warnings to errors, and has been corrected.
SR-132919 · Issue 201479
REST querystring not forced to lower case
Resolved in Pega Version 7.1.8
A Rule-Service-REST.validate activity which forced the query string to lowercase was leading to REST services are not receiving the input values in case of capital or camelCase query strings. To resolve this, the code that fetches querystring name for REST will not convert it to lower case.
SR-128332 · Issue 199072
Added detection for WSDL import failure
Resolved in Pega Version 7.1.8
Issues were encountered while importing WSDL in the ML6 environment while SoapUI was successful using the same SOAP service. This error happened when the WSDLParser.parse(Reader) was trying to read a closed java.io.Reader instance and silently generating an exception. Error handling has been added to report the failure and give an informative message.
SR-128463 · Issue 193907
Create KeyRing updated for split schema
Resolved in Pega Version 7.1.8
If a command line script is configured (viz. keyringGen.sh) to encrypt user passwords for prconfig.xml databases using Keyring utility, a prconfig.xml could have three database entries but the keyring tool only prompted for two databases and did not allow encrypting password for the user for the third database. The prconfig.xml file requires very specific location information to run: to resolve this, the variables to hold schema name in case of split schema configuration have been added.
SR-129312 · Issue 198553
Corrected HTML display of characters in reply emails
Resolved in Pega Version 7.1.8
HTML characters were appear in the email body and subject for outbound reply messages. For example, if subject is test, the reply email would display the subject as RE: test<%gt; An HTML reply to an HTML email did not contain these entities/artifacts. Reply emails can now be configured to use HTML format, and the 'HTML' option has been added to the Message Type drop-down on the Response tab of Service Email rule.
SR-131612 · Issue 200253
Handling added for accent characters in DataTable editing
Resolved in Pega Version 7.1.8
When a DataTable had a key value with an accented character like "é", clicking on the "Open this item" icon to edit the row displayed a blank page in the editor. This was caused by the escape method of native JavaScript being deprecated, and the system has been updated to use encodeURIComponent method instead.