In PRPC 5.5, a change was made to the underlying rule metadata stucture to support a tree-view display instead of a flat list of parse steps. For backwards compatibility, both old and new views are present in the rule form, and Javascript selects the correct view to display on form load based on the presence of the pyTree property. The rule form seems to get confused about this change and reports a false error on Save As that the pyParseSteps property is not found. It is a false error because the save actually succeeds, and all saves from that point on work correctly without the form error showing. The rule form was upgraded to a harness in 7.1 ML7, so this problem should not be seen again after that.

Hi Praveen,

Can you please check if pyParseSteps property is present in the rule data (do a view XML) and look for this property.

As Peter mentioned , though this error seems to be intimidating, its less serious as the save happens sucessfully as well as the runtime is unaffected.

This happens if PageData/pyParseSteps property might be missing in ruledata.

Hi,

So when do you want me to check exactly..Like do u want me to check when i save rule to new version and check xml or after chcking out and checking in the rule in the new version. Can we think that this issue is with OOTB rules Pega itself. i'am not sure whether this error is coming or not in higher versions of PRPC.

Regards,

Praveen Bala.

Hi Praveen,

Look at the Rule XML (Actions > View XML) before you even save it to the new version and definitely before you check it out. You will notice in the XML for the rule that the pyParseSteps property is missing. After you save the rule to the new version you can check the Rule XML again (the pyParseSteps property will probably still be missing). After you check out the rule and save it then check it back in you should look at the Rule XML one last time. At this point you will notice that the pyParseSteps property is now present.

Regards,

Henry

Pega Academy