SR-C6941 · Issue 343726
Rollback information collection optimization
Resolved in Pega Version 7.4
During rollback information collection, a rule inventory is regenerated. This checking can include searching for instances that no longer exist in the database, potentially causing performance issues. In order to optimize the function and reduce unneeded logging, the rollback information collection process has been updated to reuse the rule inventory.
SR-C8467 · Issue 349659
Support added for Cassandra on SunOS
Resolved in Pega Version 7.4
Changes have been made to startup scripts and lz jar version in order to support C* on SunOS.
SR-C8702 · Issue 349662
Fixed cataloging for framework hotfixes with non-java code
Resolved in Pega Version 7.4
The system was unable to catalog Strategic Application hotfixes that included non-java code instances (e.g. .xml or .properties files) due to Framework hotfixes using a different version format that caused validation failure. To correct this, the system will bypass redundant release version validation for Strategic Application hotfixes so that it can catalog non-java code instances.
SR-C8702 · Issue 344809
Fixed cataloging for framework hotfixes with non-java code
Resolved in Pega Version 7.4
The system was unable to catalog Strategic Application hotfixes that included non-java code instances (e.g. .xml or .properties files) due to Framework hotfixes using a different version format that caused validation failure. To correct this, the system will bypass redundant release version validation for Strategic Application hotfixes so that it can catalog non-java code instances.
SR-B69324 · Issue 327826
Support added for removal of empty ComplexTypes entries
Resolved in Pega Version 7.4
When using several complextypes in Stream XMLs for Connect REST integration, empty values were being passed automatically for ComplexTypes that are optional. Support for the removal of empty entries from the PageList/PageGroup property has now been added.
SR-B73008 · Issue 329204
Support added for two-letter tenant names for REST
Resolved in Pega Version 7.4
Due to HTTP/REST services using the last two characters of a token to identify whether the token was a tenantHash or a service Package, REST did not work when accessed by a tenant with a name consisting of only two characters. As comparison with only the last character is required, the extractKeys API of HTTP Service has been updated to use just the last character of a token to identify if the token is a tenantHash or a service Package.
SR-B73208 · Issue 329189
Support added for two-letter tenant names for REST
Resolved in Pega Version 7.4
Due to HTTP/REST services using the last two characters of a token to identify whether the token was a tenantHash or a service Package, REST did not work when accessed by a tenant with a name consisting of only two characters. As comparison with only the last character is required, the extractKeys API of HTTP Service has been updated to use just the last character of a token to identify if the token is a tenantHash or a service Package.
SR-B79139 · Issue 337182
Listener restart logic improved
Resolved in Pega Version 7.4
File listener was not processing the subsequent file after encountering an incorrect file. Processing resumed after re-starting the listener, but the error message resulting from the incorrect file was then added to the next successfully completed file. This has been fixed by reordering the reset logic to complete before resuming the parsing.
SR-B80397 · Issue 338678
Fixed hash map size for secure SOAP connectors
Resolved in Pega Version 7.4
A memory leak for secure SOAP connectors was traced to multiple objects with the same key being added in the hashMap during SSL processing. This was due to the PegaSecureSocketFactory class missing equals and override checks, and these have been added.
SR-B81394 · Issue 335095
Fixed hash map size for secure SOAP connectors
Resolved in Pega Version 7.4
A memory leak for secure SOAP connectors was traced to multiple objects with the same key being added in the hashMap during SSL processing. This was due to the PegaSecureSocketFactory class missing equals and override checks, and these have been added.