INC-177877 · Issue 661178
Write lock check added to avoid thread contention
Resolved in Pega Version 8.5.5
After updating the Pega platform and NBA Designer, a significant drop in performance for multilevel strategies was observed. Investigation showed that invoking a sub strategy containing external input intermittently caused a thread contention issue related to write lock. This was traced to overzealous write locking of a component where only a read lock for the thread was required, and has been resolved by adding a verification check to determine whether a write lock is necessary for a given operation before acquiring it.
INC-178938 · Issue 661497
Exception handling added for ClipboardPropertyCollection
Resolved in Pega Version 8.5.5
After upgrading from Pega v7.3 to 8.5, validating the existing strategy logic generated the error "ClipboardPropertyCollection is not a supported ILType". This was traced to the special Pega expression type PropertyCollection not being supported by IL, and has been resolved by adding logic that will throw a more appropriate exception (instead of the generic PRRuntimeException) so the event can be caught by the existing fallback logic.
INC-179879 · Issue 663006
Localization added to DelegateDescription
Resolved in Pega Version 8.5.5
Localization was not working correctly for the description of a delegated rule due to pyDelegeteDescription being defined with a non-localized Property value. This has been resolved by localizing the property value for pyDelegeteDescription.
INC-181401 · Issue 665934
Added handling for MS SQL datestamp format
Resolved in Pega Version 8.5.5
When using an Microsoft SQL Server, the browse operation was failing with an SQL error for the pyIHSummary dataset. Investigation showed there were some datasets that generated SQL statements with a date timestamp format that SQL was not able to handle implicitly, affecting browsing but not functionality. This has been resolved.
INC-182137 · Issue 662489
Multistage Prediction Logic improved
Resolved in Pega Version 8.5.5
When Predictions with Response wait time configured were executed as part of make decision, each decision that came out of the strategy caused a pxDR call to fetch the relevant model execution results and process them to stage the default outcome results for models. This has been improved by modifying the system to process the existing records rather than reading data again from pxDR.
INC-183201 · Issue 664960
Resolved error during save of a Predictive Model
Resolved in Pega Version 8.5.5
Attempting to save a predictive model in Prediction Studio resulted in the error ".pyModelProcess.pyShapes(Setmodelcontrolgroup).pyMOName: Cannot generate the component ID from the provided input. Enter at least one alphabetic character." This was traced to previous work done around defining a control group using a property reference, and has been resolved.
INC-183431 · Issue 665160
Strategy execution queries tuned
Resolved in Pega Version 8.5.5
During NBA 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-160190 · Issue 658124
Logic updated to allow page property and declare index with the same name
Resolved in Pega Version 8.5.5
A Property which was in a page list which in turn was embedded in a Page was not visible in the Report Browser. This was traced to the two properties sharing the same name, and was caused by a check which ensured only entries with unique names were added. In order to support this configuration, logic has been added to pzAddPropListForClass_TreeGrid such that if a page property and declare index share the same name, they are both added to the tree grid.
INC-166120 · Issue 657054
Parameter added to prevent name localization in Dev Studio Reports
Resolved in Pega Version 8.5.5
Running the DataTableEditorReport against a customer table translated names that matched localized values, such as "Mr. Block" became "Mr. Sperren" when the locale was set to de_DE even though the property was marked as "Do not localize" in UI Controls in the report definition filter. To resolve this, the parameter 'pyskiplocalization' has been added for use in the RRFilters_logic and while displaying the select Values popup.
INC-174756 · Issue 650538
Queue processor correctly moves items to Broken Items
Resolved in Pega Version 8.5.5
When an exception occurred while Queue Processor processed an item, he queue item was not moved to Broken Items. The error " inconsistent datatypes: expected - got CLOB DatabaseException caused by prior exception" was generated. This has been resolved by modifying the NativeSQL builder and NativeSQLBatchExecutor to allow the batch of queries to be retried. Additional changes were also added for Oracle databases to identify the correct column types.