SR-B77120 · Issue 330083
Writability check added to ClipboardPage
Resolved in Pega Version 7.4
A node level declare page was failing with a readonly exception. This was caused by the assembler generating code to write to a ClipboardPage without checking whether it was writable, and has been corrected by adding a check for isReadOnly on ClipboardPage prior to calling putString on it.
SR-B77229 · Issue 332429
SQL error codes not displayed in getContent activity execution
Resolved in Pega Version 7.4
Due to a missing catch block in the exception handling, minor SQL error codes were unnecessarily displayed in the getContent activity. This has been fixed.
SR-B77643 · Issue 327227
Apache Struts updated
Resolved in Pega Version 7.4
Apache Struts has been updated to v2.3.34 .
SR-B77778 · Issue 339718
Handling added for Microsoft Internet Explorer resize harness looping
Resolved in Pega Version 7.4
When using Microsoft Internet Explorer, the resizeHarness would intermittently enter an infinite loop after being triggered, resulting in the Menu appearing and disappearing. This has become a known issue with Microsoft Internet Explorer, and the pzpega_ui_doc_harnesssizing.js resizeHarness method has been modified to compensate.
SR-B78460 · Issue 335973
Assembly errors sent to PDC and AES
Resolved in Pega Version 7.4
A large number of com.pega.pegarules.pub.generator.UnresolvedAssemblyError exceptions were found in the PegaRULES logs with no corresponding data in PDC-Central. LogHelper methods take a Throwable as an argument to trigger an alert, and Pega7 exceptions are supposed to generate EXCP0001 alerts which are sent to PDC. However, a review of EXCP0001's show that there were no messages for com.pega.pegarules.pub.generator.UnresolvedAssemblyError -- thus the exceptions were never sent to PDC and there was no visibility to system managers. This issue also occurred with AES. To correct this, a Throwable argument has been added in oLog.error() at all the places where this alert was needed.
SR-B80222 · Issue 339229
Assembly logging enhancements
Resolved in Pega Version 7.4
Logging enhancements have been made to capture information for errors thrown at Assembly Runtime to make diagnosing these types of problem easier.
SR-B80945 · Issue 336458
Added field for additional domain used for document source
Resolved in Pega Version 7.4
When attaching a file to the work object in an IAC setup, the file was attached but the busy indicator continued to run. This was caused by cross domain name errors , and has been fixed by creating a new HTML rule "pyDomainOverride" where a domain name can be added. E.g.: document.domain = "abc.com".
SR-B81460 · Issue 333150
Corrected PM/AM switch in zh_CN reports
Resolved in Pega Version 7.4
In Chinese locale "zh_CN", the calendar datetime was showing incorrect values, switching "Post meridiem" time to "Ante meridiem". This was due to the time information for the locale checking with the English string "AM/PM" and returning as false. That caused the time to always default to AM. The logic for setting AM /PM in the dosetTime API in datetimecalendar.js has been modified to correct this.
SR-B82203 · Issue 342014
Empty hidden elements stripped when AAR proxy in use
Resolved in Pega Version 7.4
When using IIS WebServer and AAR proxy configuration with high security settings, submitting a form through Microsoft Internet Explorer with hidden input fields that did not have a name attribute resulted in a blank parameter name and value being added. This formed an invalid request that returned a HTTP 200 with no error message. Because Microsoft Internet Explorer does not ignore elements which have empty names, the code has been updated to remove name attributes on pycustomerrorsection hidden elements.
SR-B82536 · Issue 336636
Thread timeouts made configurable
Resolved in Pega Version 7.4
AES Remote threads were holding system resources for upwards of 30 seconds, leading to high levels of system resource usage in some cases. To provide customization, these client parameters will be configurable: parameter http.connection.timeout = 15000 parameter http.socket.timeout = 15000 via optional DSSs: OWNING RULESET=Pega-Engine SETTING PURPOSE=prconfig/pdcconfig/connectionTimeout/default OWNING RULESET=Pega-Engine SETTING PURPOSE=prconfig/pdcconfig/socketTimeout/default If they are not configured, the default timeout (15000) will be used. Additionally, the SOAPAppenderPega sendEvent method close() method will be called if an error occurs while sending a message, avoiding the 30s wait for a connection from the pool.