SR-C6486 · Issue 349824
Check added for Kafka dataflow error handling
Resolved in Pega Version 7.4
When an event dataflow has failed because too many errors were detected, it is possible to continue it. However, it was noticed that the "continue" button had to be used twice: The first time, the dataflow failed again and the "Input record" was increased more than expected. For instance, if the event flow was sent 2 incorrect events, the "Input record" was increased by 3 instead of 1. The second time, the event dataflow was resumed correctly. Investigation showed that when a bad record is inserted into Kafka, a dummy error record is generated that has no information of the partition and position, so the data flow cannot update the partition table correctly. In order to correct this, the partition and position information will be given on the error record. The data flow execution has also been updated such that when there is an onError call, a check will be performed to assess whether the error originated on the primary source and an input record is present. If so, then the partition table will be updated from that record.
SR-C691 · Issue 349064
VBD reworked to retrieve IH DB metadata
Resolved in Pega Version 7.4
Campaign dashboard performance was slow when accessed via the Navigation bar button PRPC user configured for app server has restricted access to schema metadata. This causes VBD to be unable to build SQL query used to synchronize Actuals data set with Interaction History. It was possible to optionally configure vbd/useTableMapping = true in PR Config or DSS (owning RS: Pega-DecisionEngine) in order to force VBD to load IH database column metadata using Pega table info mapping instead of using database connection API, but the issue has now been fixed by reworking VBD to use Pega class/database mapping rules instead of JDBC DatabaseMetadata to retrieve IH fact/dim table columns.
SR-C8023 · Issue 350229
Updated dataflow used after pause/continue
Resolved in Pega Version 7.4
When using an event dataflow that has a Kafka dataset as the source, running the flow, pausing it, and importing updated rules was resulting in the resumed flow still using the old rules. This was a known limitation in the data flow metrics management where when a run was resumed, the previous metrics were "merged" with new metrics. In cases where the structure of a data flow changed between pause/resume, merge failed silently and new metrics were not saved to the database. The metric management has now been updated to merge metrics correctly: in case of a data flow structure update (e.g. shapes added/removed), after the data flow is run, stage metrics will be cleared up as it is not possible to match them with the new structure, and all other metrics will be properly resumed from the "paused" position (e.g. number of processed records, throughput etc.).
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.