Question
Cognizant
IN
Last activity: 23 May 2023 1:36 EDT
How to make a property not to save in pzpvstream
The scenario here is :
suppose we're having two properties example Name and age on submit of the screen i don't want to save the data in pzpvstream how we can achieve it.
Accepted Solution
Updated: 23 May 2023 1:36 EDT
Areteans Tech
AU
Coforge
IN
@vimalchandvyou can do property optimization.
which means exposing a property. It will create a separate column in the database with the name of property that is exposed. And hence this will prevent the property from getting stored into pzpvstream.
Evoke Technologies
US
@vimalchandv I don't think so, even if we optimize or expose it, still the data will be there in pzpvstream as well as in column..!
Areteans Tech
AU
@AkshithReddyT In the Property Rule , under Advanced Tab , you can use "do not save the Property Data". try that !!
Evoke Technologies
US
@uashok93 That option will be there only for un-optimized columns right? So for optimized properties, the data will be there in both the columns right?
Accepted Solution
Updated: 23 May 2023 1:36 EDT
Areteans Tech
AU
@AkshithReddyT Hmm, I would first check if the property value needs to be stored or not, then i will think about optimization. If i dont have to save the property value , I would not optimise the property as well.
Sample use case : Consider on DOB, I have to show Age on the screen.
I don't have to store the Property Age in the DB. I can calculate the Age based on DOB anytime. In this case, I will have the Age property and will not save the data in DB and will not optimise it as well .
HCL Technologies Ltd
IN
Hi @vimalchandv,
Please find the below link for a better understanding
https://docs-previous.pega.com/system-administration/87/optimizing-database-properties
Regards
Mohd Qizer Uddin
@AkshithReddyT Hmm, I would first check if the property value needs to be stored or not, then i will think about optimization. If i dont have to save the property value , I would not optimise the property as well.
Sample use case : Consider on DOB, I have to show Age on the screen.
I don't have to store the Property Age in the DB. I can calculate the Age based on DOB anytime. In this case, I will have the Age property and will not save the data in DB and will not optimise it as well .