SR-B79966 · Issue 329488
Removed field validation for read-only labels in grid header
Resolved in Pega Version 7.4
Labels that were marked required did not switch to the explicit "required" text when accessibility was enabled. The underlying issues is that the grid column header is simply a label and configurations like "Required" do not apply to the column header. As a result, this configuration has been re-worked for consistency by disallowing/removing setting the grid headers as required. This is handled via a visibility check so that the required field validation is not displayed for labels in the grid header. The check essentially hides the required field configuration for any label inside the grid due to the label control being read-only.
SR-B91454 · Issue 340080
Click to refresh harness works the first time
Resolved in Pega Version 7.4
After configuring "Refresh Current harness" and Data transform on click of a button, the actions were not fired on the first click but worked on the second. This consistently happened when using Microsoft Internet Explorer and Edge, and was intermittent in Firefox and Google Chrome. This was traced to the click event not getting added to the queue since the queue already had a click event, and has bene fixed.
SR-C1517 · Issue 347449
Localization added for delegated decision rule options
Resolved in Pega Version 7.4
Localization has been added for the following options in the delegated decision rule: 1.Load Table in Ruleform 2.Remove Table form Ruleform 3.This decision table contains more than x cells. For optimal . . .
INC-143121 · Issue 610732
Timeout for loading predictors made configurable
Resolved in Pega Version 8.3.6
When using an extremely large number of predictors, the Report definition pzADMPredictorsFilter was suffering timeouts due to the time for loading predictors from the database exceeding the time threshold allowed. This has been resolved by marking the rule as editable to allow custom setting of the threshold according to need.
INC-148899 · Issue 615702
Adaptive models update correctly
Resolved in Pega Version 8.3.6
Some models had the recorded responses column updated, but the models (number of Positive, Negative and Processed Responses) were not updated. Investigation showed that deleting the modelRuleConfiguration through the stateManager/client did not delete modelFactories related to the configuration. If a new configuration came in with a different algorithm, the update issue occurred. This has been resolved by reseting the configuration according to its factory in that specific case.
INC-155822 · Issue 618267
Locking added to avoid null pointer error for auto-populate property
Resolved in Pega Version 8.3.6
After configuring the auto populate property "OrgProduct" which referred to a data page, the system experiencing heavy load led to the property not getting properly initialized. This resulted in a WrongModeException and NullPointerException. To resolve this, the system has been updated to lock the requestor when Queue Processors execute their activity. This will prevent race conditions and concurrent modifications if other threads are accessing the same requestor.
INC-157629 · Issue 626633
Duplicate key exception resolved for adaptive model
Resolved in Pega Version 8.3.6
During the model snapshot update, a DuplicateKeyException was generated while trying to insert a record in to the predictor table. This did not affect the model's learning, but did appear ion the model monitoring report. This was traced to a local scenario of having the same outcome values defined on the model with different cases (Accept and accept). All predictors used in an Adaptive model are inserted into the model monitoring tables as a part of the monitoring job: because the monitoring tables are not case sensitive, this lead to a unique constraint exception since there were multiple IH predictors with the same name. To resolve this, validation has been added which will skip adding duplicates from new responses.
INC-160331 · Issue 628710
ML model continue tag error changed to debug logging
Resolved in Pega Version 8.3.6
Log entries were seen indicating "The continue tag is found without a start tag for window Line1 1234567890 in text". This appeared to be coming from the MLCommand java class. Investigation showed this occurred when the ML model believed a portion of the text (token) was a continuation of the entity because it has not found the starting part of the entity. This situation is not currently treated as a valid output, so an update has been made to change the logging level from error to debug for this case.
SR-69015 · Issue 619995
Unescaping characters implemented for expressions
Resolved in Pega Version 8.3.6, Resolved in Pega Version 8.4.4, Resolved in Pega Version 8.5.3, Resolved in Pega Version 8.6
An issue where expression builder statements were evaluated differently at runtime than at testing has been resolved. Pega Platform expressions with String literals(that is, sequences of characters enclosed in quotation marks) now unescape characters in strategy shapes such as Set Property or Filter.