Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

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.

SR-A6740 · Issue 214445

Bulk delete activity added for ADM models

Resolved in Pega Version 7.2

In order to support the deletion of ADM models in bulk, an enhancement has been added to remove the unwanted models from the database provided a list of them is given as input. The activity pxDeleteModelsByCriteria has been created; "Used to delete ADM models in bulk. Models to be deleted are determined by the criteria selected by this Activity's parameters; a model is deleted if it matches all selected criteria."

SR-A8236 · Issue 217334

Data flow respects vertical scalability settings

Resolved in Pega Version 7.2

The number of threads per node specified in Decision->Simulation Settings->Topology landing page was not taken into account by data flow execution, leading to the inability to configure vertical scalability per PRPC node and/or exclude certain nodes from data flow execution. This was an error where the configuration was being ignored and a default value was always used, and has been corrected.

SR-A5666 · Issue 215313

Flow Image available in "WhereAmI" option of iframe

Resolved in Pega Version 7.2

In some cases, it was not possible to see a flow canvas when the request was made from external system (e.g.. calling Pega URL from iframe). The framework was not taking into account the case where the frame was embedded in a document from a different domain. The cause of this issue is that the iframe and the parent frame have different origins, which prevents Viewer Data registering correctly. The system has been updated to detect whether the parent frame has the same origin as iframe, then choose correct the parent context to register Viewer Data. The object used to contain viewer data should be created in the right context in order to avoid cross origin exceptions.

SR-A7256 · Issue 218467

Flow image resolution now set by default

Resolved in Pega Version 7.2

In some flows with widely spaced shapes, the resolution of the flow image was insufficient- i.e., the text inside the flow shapes is not legible. The flow image is captured at a user defined zoom level, causing the captured flow images to have non-uniform resolution. The image capture now is done at a default origin and zoom level. The image capture will then restore the user selected zoom level after the capture happens.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us