OOTP temporary Pega properties like pyTempText, pyTempDate can be saved
We were using pySearchText property in a specific searchtype in our app, and noticed that in some rare edge cases this gets saved to the database causing some unwanted sideeffects for us.
This could be easily avoided with using another property here, which is not savable.
However, we would like to have a better understanding about why these OOTB temporary Pega properties like pySearchText, pyTempText, pyTempDate, pyTempInteger on @baseclass and pyTempValue on Embed-Display-Table-Cell class are all savable. Our understanding is that all these properties are for temporary use, thus saving these could result in unexpected side-effects.
Lantiqx Limited
IN
Hi ,
We can refer and update the properties that starts with py (for example : pyNote,pyLabel) but we can refer properties that starts with px .
After setting the properties by using py properties we can use them through out our case processing . but to save them in our data type you need to map it to the properties related to data type
Saltech Consulting
HU
@Siva Naga Syam Kumarwe understand how the system works, the question is rather about why it works like this. What's the benefit of these properties being savable? We don't really see any benefit, however we faced some unwanted sideeffects because of these settings.