SR-C7742 · Issue 349877
Proper cleanup for leftover clipboard pages after sync
Resolved in Pega Version 7.4
When the stateful sync requestor has finished, all pages that are replaced on the next sync should be removed. Several pages were found to not be cleaned up as expected, and this has now been corrected.
SR-C8899 · Issue 349868
ABAC exception handling added
Resolved in Pega Version 7.4
After creating an access control policy and access control policy condition on a data class that shows in the Data Explorer, defining the condition such that it was always false and then clicking on the class on which the policy was just defined generated an error. If the policy was withdrawn and then clicked on again, it appeared as expected. This was reproducible only when ABAC was enabled, and handling for an exception generated in this scenario has been added.
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.
SR-B83049 · Issue 337923
Expose API works in multitenant environment
Resolved in Pega Version 7.4
Invoking the OOB Service-REST "Expose" from Pega API threw a bad class definition error when run in a multi-tenant environment. This was due to the expose operation in a multi-thread environment running in shared context instead of tenant context, and an enhancement has been added to run it in tenant context instead of shared to solve this issue.
SR-B85654 · Issue 337379
Response timeout fixed in REST
Resolved in Pega Version 7.4
The "Response Timeout" option in REST connectors was controlling only the SO_TIMEOUT attribute, which defines a socket timeout, and did not set the CONNECTION_TIMEOUT. This caused REST connectors with this setting set to not time out as expected, and was due to the HttpClient connection time out setting being missing in the client initialization. To fix this, the connection timeout has been added and will be the same as the socket timeout in HttpClient.