INC-185045 · Issue 672419
Performance improvements for action check-in
Resolved in Pega Version 8.4.6
The process of 'Saving As' an action to a higher ruleset, Saving, and then running Check-in was taking an excessive amount of time. This was traced to redundant page copy activities and performance has been improved by updating the implementation.
INC-186437 · Issue 669187
Updated entity attachment extraction tokenizers
Resolved in Pega Version 8.4.6
After creating an entity extraction model, it was seen that one of the entities worked when there was a space after the semicolon but the detection was not working if there was no space. This has been resolved by updating the Tokenizers with extra examples to address tokenization when ":" is present between two words without any spaces.
INC-186889 · Issue 674016
Unused DSS compiledExpressions now defaults to false
Resolved in Pega Version 8.4.6
After updating from Pega 8.2 to Pega 8.5, executing a test campaign failed with an error in logs. This occurred when running Distribution tests with "Include funnel analysis reports" checked, and was traced to the DSS setting "decision/strategy/ssaVM/compiledExpressions". As this was previously used to toggle a feature which is no longer in use, the default setting for this DSS has now been changed to false to resolve this issue.
INC-187070 · Issue 672107
Strategy execution queries tuned
Resolved in Pega Version 8.4.6
During Next Best Action strategy execution, interaction history summaries were queried multiple times for a single strategy execution. To improve this function, the isChanged query will now be executed once after system startup if there are no changes instead of being executed every time the Aggregates DataSet BBK is executed. If the same Aggregates query is made multiple times as part of a Strategy in a REST request (i.e. likely multiple ADM models in a MakeDecision call), only one Aggregates BBK call will be made.
INC-189136 · Issue 679518
Dataflow with report definition source repaired
Resolved in Pega Version 8.4.6
After update, data flows using a report definition dataset as source were throwing a null pointer exception. This was traced to previous work done around retry handling for Oracle queries where there were issues identifying the correct column types; that previous work has been reverted to resolve this null pointer exception, and further work will be done to refine the solution to the Oracle CLOB DatabaseException.
INC-192102 · Issue 676362
Performance improvements for stale thread warnings
Resolved in Pega Version 8.4.6
Stale thread warnings were causing performance issues during dataflow run execution. Stale thread/slow component warnings are added as part of the dataflow execution when a processing thread takes more than 5 minutes to process a single dataflow record. The stacktrace of the dataflow thread is added as part of the warning for debugging purposes, but in some scenarios the stacktrace can become very large. This has been resolved by removing the stacktraces from the warning, improving the query logic, and adding the run ID to the exception method to assist if there is an error.
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.