SR-D85095 · Issue 546342
Updated COUNT logic for strategies with ssavm set to true
Resolved in Pega Version 8.4.1
An error was seen when attempting to save a strategy after setting ssavm to true, indicating an issue in the “COUNT” method in Group By shape. Since the source field is not used and does not need to be evaluated here, the system has been updated to ignore the source field if the operation is COUNT.
SR-D85558 · Issue 548287
Handling added for prolonged Heartbeat Update Queries
Resolved in Pega Version 8.4.1
After restart, the pyFTSIncrementalIndexer queue size had hundreds of thousands of entries even though it was empty prior to the restart.Investigation traced this to a job scheduler that checked all the database connections everyday at 1 EST by using a list that contained some connections which did not exist. Checking those invalid connections caused other update queries to queue and wait, resulting in the update heartbeat query taking longer than its default beat. This caused a Split Brain issue wherein other nodes considered the long-executing node to be dead and triggered a rebalance while the node itself continued to execute partitions thinking that it was healthy. This caused duplicate processing of records. To resolve this, a fail safe has been added: while updating heartbeat in Service Registry, nodes will enter safe mode when the update query is taking longer than the default beat.
SR-D89012 · Issue 550801
DelegatedRules refresh icon made accessible
Resolved in Pega Version 8.4.1
When using Accessibility, the refresh icon in pzDelegatedRules was being read as "Link". This has been corrected by adding text for the refresh icon.
SR-D89428 · Issue 550393
Data Flow StartTime uses locale timezone
Resolved in Pega Version 8.4.1
The start time of the dataflow was displayed in GMT instead of the operator locale timezone. This has been corrected.
SR-D89643 · Issue 548293
Old Tumbling Time data in event strategies given TTL for cleanup
Resolved in Pega Version 8.4.1
Old Tumbling Time data keys in event strategies were not being cleaned up, causing Cassandra timeouts after the dataflow run had been running for several months. The longer the dataflow was running using standard compaction, the more the data was potentially spread out across SSTables and the slower it became. This has been resolved by adding a 'time to live' value for tumbling time windows, and event strategies has been switched to use leveled compaction by default.
SR-B56256 · Issue 335795
VBD cache handling changed to preserve data integrity
Resolved in Pega Version 7.4
When VBD was configured to use on-heap memory, no data was displayed in VBD planner and logs showed queries failing with ArrayIndexOutOfBoundException. The cause of the error was a corruption of VBD cache data in a partition: VBD compresses its partitions after getting no inserts for 15 minutes. When an insert is received by a compressed partition, the partition is first decompressed before writing. During decompression, the buffer position is set to the end of the uncompressed buffer. However, the buffer may include padded nulls added during buffer expansion. The system writes the new VBD records after the padded nulls, but the nulls would then throw off the read logic during query execution. To fix this, during decompression the buffer position will now be set to the end of the data, not the end of the buffer.
SR-B56256 · Issue 337432
VBD cache handling changed to preserve data integrity
Resolved in Pega Version 7.4
When VBD was configured to use on-heap memory, no data was displayed in VBD planner and logs showed queries failing with ArrayIndexOutOfBoundException. The cause of the error was a corruption of VBD cache data in a partition: VBD compresses its partitions after getting no inserts for 15 minutes. When an insert is received by a compressed partition, the partition is first decompressed before writing. During decompression, the buffer position is set to the end of the uncompressed buffer. However, the buffer may include padded nulls added during buffer expansion. The system writes the new VBD records after the padded nulls, but the nulls would then throw off the read logic during query execution. To fix this, during decompression the buffer position will now be set to the end of the data, not the end of the buffer.
SR-B67003 · Issue 329137
Enhancement added to validate mandatory fields in custom proposition definition forms
Resolved in Pega Version 7.4
Enhancements have been added in order to support extended customization of a proposition definition form. Previously, the custom form containing the custom fields was rendered in the context of a requestor-level, editable data page for creating a new proposition. The custom form section itself did not belong to the same class as the data page but was only rendered in the context of the data page at run-time. Therefore, validations defined on the custom form were not triggered due to the mismatch in the context of execution. The system has now been updated with an extension activity which will have the required-field validation pre-loaded. The same activity can then be extended to include additional validations whenever needed. The approach has some limitations as below. Process: On the custom form for the proposition group, the appropriate fields will need to be marked as required-always from the 'Required' dropdown field configuration form. After this, with the local fix branch included, new propositions should be validated for missing required fields. Limitations: The validation will work only on the manual creation of a new proposition. Conversely, the validation will NOT work if the propositions were uploaded using the Import/Export feature on the Decision Data form. The validation error messages for the custom fields will appear on the top of the page unlike that for the proposition name property. However, the message will list all properties that are marked as required but haven't been filled-in on the form.
SR-B72990 · Issue 326318
DataFlowGenerator class files preserved longer
Resolved in Pega Version 7.4
When creating a campaign, running the generated data flow manually resulted in an illegal argument exception indicating a null property name. This was traced to the use of an overwrite data flow API: class files were generated and removed immediately after the DataFlow object is constructed. In some cases, the java classloader may delay loading of the classes, causing the NoClassDefFoundException as files have been already removed. To resolve this, the DataFlowGenerator will now wait one day to remove the classes.
SR-B75057 · Issue 328508
CSV import of list segment fixed
Resolved in Pega Version 7.4
After upgrade, CSV import of a list segment in Pega Marketing was not working if the header name was "WorkEmail" in LMMS. This was due to a redundant call made to pxgetFilteredUniqueKeysListFromDB, and the code has been updated to correct this.