Question
American Express
US
Last activity: 29 Oct 2015 12:46 EDT
Scalar properties are being set as Pages (Pega 7.1.6)
HI Team,
I am getting the below issue, when i search through PDN I got this hot fix : HFix-9495. PDN Link Node ID: 240811
Is this issue present in Pega7 also
In the tracer we got the below fail msg first
WrongMode pyWorkPage.TotTimeAdmit Page adoptDictionaryDefinition(ImmutablePropertyInfo, boolean, boolean) String the mode has been reset to match the property's definition.
Later it is getting failed at obj-save on the page.
Trying to save an invalid page: Trying to save an invalid page: page is not valid .TotTimeAdmit: The property SelFeature.TotTimeAdmit was of mode Page while adoptDictionaryDefinition(ImmutablePropertyInfo, boolean, boolean) was expecting String mode. Details: the mode has been reset to match the property's definition.
Our property TotTimeAdmit is Double which is a scalar property. If i stall this hot fix will this solve my problem. If yes can you please provide this Hot-Fix
Regards,
Manoj
Updated: 29 Oct 2015 10:35 EDT
Hotfixes are specific to a single version. This hotfix is for 6.3 SP1. I'm investigating at what point this issue is corrected natively. 7.1.6 is several versions old, so it is likely that the issue addressed by this hotfix was not corrected until a more recent version.
Update: The issue corrected by this hotfix is natively fixed in 7.1.6. The issue that the hotfix corrects is specifically caused by setting the value on a "single value/text" property using Property-Set method in an activity, after the property has been deleted from the database, which causes an embedded page to be created ( instead of value being set a scalar value.)
That doesn't appear to be the issue you're encountering here. I would recommend opening a support request.
Accenture
US
Assuming it is not a native Pega problem -
The first and second error do not seem related to me given the information you gave. Is pyWorkPage a different class than SelFeature? TotTimeAdmit could be different properties named the same, with different types, in different classes.
Another thing it could be is if you used an activity to set TotTimeAdmit as a page somehow on SelFeature. Then do an obj save on SelFeature. Normally you do not want to be saving work pages in activities.
If you tried changing the type of a property, that no longer seems to work in Pega 7. You have to delete the property and remake it. This also requires a database change if you name the property the same and it has been previously optimized