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.
SR-B82651 · Issue 334646
BIX Extract stale thread error resolved
Resolved in Pega Version 7.4
BIX extracts executed from Agents results were failing intermittently, displaying exceptions from PAL and threads. This was caused by the ExtractImpl code using static variables for threads, leading to threads being recycled. To resolve this, the variable gThreadCmdLine has been changed to use instance instead of static(class level) in ExtractImpl.
SR-B83101 · Issue 333215
Support added for custom URL format
Resolved in Pega Version 7.4
The application was not allowing the use of URLs ending with any format except .com and would generate a validation exception. This was traced to the system using Apache commons URLValidator class for validation of URLs, and that program does not allow custom domains. To compensate for this, a new validate rule 'pyValidateWrapper' has been made available, which will call pxValidateURL. In addition, the AttachURL activity has been modified to call pyValidateWrapper instead of pxValidateURL so customized validation logic can be inserted.
SR-B83251 · Issue 340712
Logoff null-pointer exception fixed
Resolved in Pega Version 7.4
An null-pointer exception was being generated while logging out from Pega. This was traced to the ThreadContainer.get() returning as null during async data page clean up from the thread, and the handling has been changed to ensure the ThreadContainer is not cleared before all the pages from the thread get cleaned.
SR-B83559 · Issue 331464
Special German characters encoded in URL
Resolved in Pega Version 7.4
Microsoft Internet Explorer was not encoding some German characters, resulting in unexpected special characters being sent to the engine in a URL as parameters that resulted in crashing the application. The HttpAPI and URLComponentProcessor have been modified to solve the issue by encoding the queryString if it isn't already encoded.
SR-B85212 · Issue 338429
Presence Session State Tracker Daemon honors operator presence setting
Resolved in Pega Version 7.4
The Presence Session State Tracker Daemon is meant to be started only if operator presence is enabled (the default), but the system was running it and trying to shut down the daemon even when the feature was off. A check has now been added to ensure the operator presence feature is honored.