Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Incorrect behavior on updating versioned Adaptive model

SA-92832

Summary



On updating an Adaptive model in a branch after versioning the model, the changes made display on the UI. However, the changes are not saved to the database.


Error Messages



Not Applicable


Steps to Reproduce

  1. Open the Pega Prediction Studio.
  2. Open the Adaptive Model rule that must be updated.
  3. Navigate to Actions > Save As. Note the Predictor Types of the first page of predictors.
  4. Select a Development branch.
  5. Click 'Create and open'.

Root Cause


A defect in Pegasystems’ code or rules: Adaptive Model rule UI in both Prediction Studio and Dev Studio.
When a non-default Predictor type is selected, the change made displays on the UI, but is not saved to the database. An error does not display during the Save. Hence, incorrect data is stored. That is, when data has accrued, the rule cannot be Saved or Saved As because Validation starts, believing that the Predictor type of a Predictor with data is changing.


Resolution



Perform the following local-change:
  1. Create a new Adaptive Model rule (or Private Edit an existing rule).
  2. Add a field Predictor based on a property of the class. On selection, the property type and Predictor type of the row are filled with the default values.
  3. Change the Predictor type to another available value.
  4. View the XML of the rule through the Actions menu. Confirm that the new Predictor is in both the pyStaticPredictors and pyPredictors list elements and that the value for the pyPredictorType element is the same as on the UI.
This feature is implemented in Pega Platform 8.2.5.
Suggest Edit

Published July 4, 2020 - Updated December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

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

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us