INC-162262 · Issue 654964
Query added to find time zone for MSSQL database
Resolved in Pega Version 8.5.5
The exception "com.microsoft.sqlserver.jdbc.SQLServerException: xp_regread() returned error 5, 'Access is denied.'" was generated when the AES agent PushDBSizeInfo was being run. This was traced to the GetDBInfo activity trying to retrieve the time zone of the MSSQL database by executing a query that used a Microsoft SQL routine to read the windows registry to get the current time zone. The error was not due to security within the SQL Server, but instead was caused by Microsoft Windows security related to the permissions on the registry keys for the users under which specific SQL Server processes were running. To resolve this, an update has been made to call a different query which will get the time zone for the SQL Server.
INC-162262 · Issue 658949
AES call to mbean disabled
Resolved in Pega Version 8.5.5
Under certain conditions, the AESRemote 'push memory' agent call to the legacy memory management mbean caused unexpected behavior in declarative rules for work running in data flows and queue processors. This has been resolved at this time by overriding the push memory usage agent activity to skip mbean and connect REST.
INC-169116 · Issue 654255
Correct time zone chosen for fr_Fr appointment function
Resolved in Pega Version 8.5.5
When using the "fr_Fr" location and and "Europe/Paris" time zone for appointments, a null pointer exception was seen related to the function getStartOrEndDateTime. Investigation showed that the incorrect time zone was being picked from the fr_FR.xml file when parsing the date. To resolve this, 4 letter time zone codes have been moved above the 3 letter time zone codes.
INC-170551 · Issue 656558
Rule Assembly update for pxTextInput and pxDisplayText
Resolved in Pega Version 8.5.5
After the application restart, multiple rule assembly alerts were seen for pxTextInput and pxDisplayText . During first access, Assembly is done and container is cached in VTable; investigation showed that in this case, the Load class without the package name had a class not found issue, and then subsequent access tried to use the container from cache and assembly was not done. To prevent this, an update has been made to perform the class lookup using the package name and class name.
INC-170646 · Issue 658306
Security update for unauthorized URL requests
Resolved in Pega Version 8.5.5
Updates have been made to improve security around unprivileged users and unregistered requests.
INC-172350 · Issue 658276
Removed duplicate Set-Cookie Secure Keyword
Resolved in Pega Version 8.5.5
Checking the headers of the login page showed the Cookie Pega-AAT duplicated the Secure keyword. This was traced to the PegaAATCookieWrapper extending the CookieWrapper class and causing the secure flag to be set in both the classes. This did not have a functional impact, but the secure flag set has been removed from the PegaAATCookieWrapper class to avoid duplication.
INC-172859 · Issue 661201
Invalid date handling added to Legacy Adapters
Resolved in Pega Version 8.5.5
Running the Job Scheduler activity failed with the error "not a valid date/time value". Investigation showed this was caused by LegacyPropertyAdapter.isEmpty being returned as true in case of properties having invalid values, and has been resolved by adding handling for an InvalidValueException in LegacyPropertyAdapter and LegacyPageAdapter.
INC-173392 · Issue 650243
Metadata space out of memory Healthcheck failure propagates correctly
Resolved in Pega Version 8.5.5
When an "OutOfMemoryError:MetaSpace" was generated from PRClassLoaderDB.loadClass, the exception was not propagated from its caller method. This has been resolved by adding the hook to call HealthMonitorService().processCriticalError in PRClassLoaderDB.loadClass(). HealthCheck will be set to 'UNHEALTHY' based on errors configured in GenericErrorAnalyzer, which includes an out of memory condition.
INC-173436 · Issue 648820
Performance improvement for Application Save: Node Level Data Pages
Resolved in Pega Version 8.5.5
As part of new functionality introduced in 8.3, data types defined in the application record will be turned into data objects on Application save. As part of this process node level pages are invalidated and reloaded and there is an explicit commit that marks the Application record as dirty and sends any calls for the application record to the database for fresh records. In a multi-node environment, the number of queries to get the application record being saved became exponentially higher and performance impacts were seen. This has been resolved by updating the system to skip eager loading of the data page definition when an access rule or application definition is saved.
INC-173895 · Issue 655914
ZMW added to currency codes
Resolved in Pega Version 8.5.5
The Zambian Kwacha, "ZMW", has been added to the currencies code list in ENCurriencies.xml .