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.
SR-B85428 · Issue 335759
setClassName() API clears the cached dictionary info
Resolved in Pega Version 7.4
An exception was seen relating to the pzGuardrailsFilterValidation activity, causing cached classInfo to not be cleared when pxObjClass was overridden. This was an issue with some of the APIs which change the value of pxObjClass not clearing cached classInfo, causing getClassInfo().getClassName() to return the previous value of class, and the system has been updated to ensure the setClassName() API clears the cached dictionary info.
SR-B85680 · Issue 341307
Ensured update details passed to WO conflict message
Resolved in Pega Version 7.4
With optimistic locking, when SLA is processing the work object and the assignment is submitted, the conflict information message shown to was blank. This was due to the Assign-.ExecuteSLA activity workPage being saved using Obj-Save, leading to the work page's pxSystemUpdateDetailsList not being populated and not having anything to pass when the page list is later used in preparing the conflict message. This has been fixed.
SR-B87340 · Issue 336754
MaxFileSizeViolation honored by Firefox
Resolved in Pega Version 7.4
When using Firefox, the out-of-the-box pzMultiFilePath control was not preventing the upload of a file size greater than the pyMaxDragDropAttachSizeMB system settings if a file exceeding the threshold was selected after a valid one (within size limit). When the modal dialog was closed, clicking on the "Attach" button resulted in both files being uploaded to the pega_temp/StaticContent/global/ServiceExport path. This was caused by Firefox not following a global symbol for "event" (which Google Chrome/Microsoft Internet Explorer do), and the code has been updated to prevent a MaxFileSizeViolation.
SR-B87483 · Issue 335816
Corrected blank screen in fr_FR language pack
Resolved in Pega Version 7.4
After the French translations were imported and the operator locale was set to fr_FR, a blank screen appeared. This was due to missed error handling in the translations pack, and code has been added for the variable gStrFeatureNotSupportedInBrowser to avoid a blank homepage when using the French language pack.
SR-B87521 · Issue 336008
Performance improvements for opening a Data instance
Resolved in Pega Version 7.4
Logic improvements have been made to improve the performance of opening a Data instance from rule explorer.