SR-D83053 · Issue 544268
SameSite cookie setting added for Mashup support in Google Chrome v80+
Resolved in Pega Version 8.2.6
The Google Chrome browser version 80 and above now treats SameSite with a blank value as "Lax" by default, causing mashup scenarios to break. In order to compensate for this change, support has been added for setting SameSite=None in Cookie Settings in the CSRF LP (DevStudio-> System-> Setting-> CrossSiteRequestForgery) which will enforce HTTPS for the Pega server and mashup. Note: The SameSite cookie may be set to None/Lax/Strict, based on the requirement. For mashups to work, SameSite should be set as None. To follow proper security standards, it should be set as Strict.
SR-D83192 · Issue 545057
JobScheduler DST handling updated
Resolved in Pega Version 8.2.6
When the locale being used changed out of Daylight Savings Time, scheduled jobs did run at the same local time as before but instead ran an hour earlier than expected. Investigation showed that jobscheduler calculated the next runtime based on the time difference from the cluster reference time and current time in milliseconds, and this offset in milliseconds was added to next run time. Since the cluster was started in DST, the job was running on same time due to the time difference. To resolve this, the system will use a calculation offset and set hours/minutes to nextRunTime object so that calendar lib handles daylight savings.
SR-B65434 · Issue 334578
Oracle table metadata performance improvements
Resolved in Pega Version 7.4
Performance improvements have been added for Oracle table metadata queries.
SR-B74189 · Issue 334576
Oracle table metadata performance improvements
Resolved in Pega Version 7.4
Performance improvements have been added for Oracle table metadata queries.
SR-B76468 · Issue 336009
Oracle table metadata performance improvements
Resolved in Pega Version 7.4
Performance improvements have been added for Oracle table metadata queries.
SR-B76989 · Issue 327639
Informational text added to "No suitable driver" error message
Resolved in Pega Version 7.4
After configuring Pega to connect to an external database using Data-Admin-DB-Name with a JDBC URL configuration that had the appropriate jar for the driver in the application server classpath, unexpected behaviors were seen. The first time the Test Connectivity button was clicked, a "No suitable driver found" error appeared. The second click ran the test as expected. This confusion was related to an undocumented enhancement: because adding a new database JDBC driver in Pega may require configuration to get the driver class loaded to the classpath, the 'No suitable driver' exception was enhanced with the configuration required to get the JDBC driver loaded at the next restart. In order to avoid confusion, informational text will now appear as part of the "No suitable driver" error message to explain this.
SR-B82933 · Issue 333921
SQL queries constructed to stay below 1000 limit
Resolved in Pega Version 7.4
A very large SQL query referencing a large number of history classes was generating an SQL syntax error exception due to exceeding the maximum number of expressions in a list (1000). In order to support large queries, the SystemManagementUtils.generateWhereINClause function will now construct queries that stay below that limit per single query.
SR-B86451 · Issue 334135
SQL queries constructed to stay below 1000 limit
Resolved in Pega Version 7.4
A very large SQL query referencing a large number of history classes was generating an SQL syntax error exception due to exceeding the maximum number of expressions in a list (1000). In order to support large queries, the SystemManagementUtils.generateWhereINClause function will now construct queries that stay below that limit per single query.
SR-B89556 · Issue 341256
fixed exception for relaystate with more than 128 characters with DB2
Resolved in Pega Version 7.4
In IDP initiated SSO, an SQL error was generated when using DB2 and the relaystate contained more than 128 characters. This was caused by DB2 validating the column length of the 'where' clause column, and those column bytes exceeding the declared length of 128. This has been fixed.
SR-B90273 · Issue 339015
Corrected assembler SQLSyntax error
Resolved in Pega Version 7.4
If an install was done with the --assembler=true option, certain generated SQLs weren't schema qualified. This resulted in a 'table not found' error and the install failed. This has been resolved by correcting the class identifier references in the cache.