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

Unable to save a workitem after upgrade

SA-88314

Summary



Post upgrade to Pega Platform 8.2.1, unable to save a Claim work item.


Error Messages



TempWorkPage.ClaimData.NoticeData.InsuredEconomicLoss(1).EconomicLossDetails.LocationAddress.FeaturePage WrongMode
TempWorkPage.ClaimData.NoticeData.InsuredEconomicLoss(1).EconomicLossDetails.LocationAddress.FeaturePage String adoptDictionaryDefinition(ImmutablePropertyInfo, boolean, boolean) Page the mode has been reset to match the property's definition.

TempWorkPage.OldNoticeData.InsuredEconomicLoss(1).EconomicLossDetails.LocationAddress.FeaturePage WrongMode
TempWorkPage.OldNoticeData.InsuredEconomicLoss(1).EconomicLossDetails.LocationAddress.FeaturePage String adoptDictionaryDefinition(ImmutablePropertyInfo, boolean, boolean) Page the mode has been reset to match the property's definition.



Steps to Reproduce

  1. Upgrade Pega Platform  7.1.6 to Pega Platform 8.2.1.
  2. Launch the Pega application.
  3. Configure a duplicate property in the Inheritance path.
  4. Initialize the duplicate property to create a work item.
  5. Save the work item.

Root Cause



An issue in the custom application code or rules.
The duplicate property was in the same Inheritance path but with a different property mode.



Resolution



Perform the following local-change:
  1. Withdraw the duplicate property.
  2. Create a new property with a different name.

Published March 19, 2020 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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