Support Article

Class key validation issue on field value

SA-13587

Summary



Developer is observing class key validation issue on field value whenever they move from one environment to another environment.
They are on multi node environment with same prconfig file settings across all the nodes.


Error Messages



Class Key validation failed for class: Rule-Obj-FieldValue, class key value: X-X-X, reason: Instance not found

Steps to Reproduce


 
  1. Create a property and use UI control as PromptFieldValue.
  2. Create a field value for the property created.
  3. Execute the flow.

 

Root Cause



An issue in the custom application code or rules. Found a dynamic system setting <env name="conclusioncache/fieldvalue/pruneatage" value="7200000" /> in prconfig file. In Pega 7.1.6 with the existing code in place this setting cannot be supported for field value conclusions.

The reason behind this issue is field value conclusions are not stored in DB and only a memory cache is maintained. When the configuration has the above setting, then conclusion entries are removed from memory when they meet the age specified in setting.

Resolution



Perform the following local-change:

Remove the value from the Dynamic setting rule and restart the server.
Suggest Edit

Published September 2, 2015 - Updated October 8, 2020


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.