Question
Cognizant
CA
Last activity: 2 Sep 2017 14:08 EDT
Property change in DB, does not reflect in case
Hi All,
This is a silly question. If we change a property value (ex: pystatuswork) in the db directly for the case. the new status value is not reflected in the case. verified from DB the column value is changed successfully for the record. whereas the case shows old value only.
question is what feature in pega is preventing such dubious methods(changes made directly in DB) to not reflect in the value in the case.
version: prpc 6.1sp2
regards
Tarun
***Edited by moderator, Maryrita: moved to Product Support from Applications***
***Edited by Moderator Marissa to update categories***
Pegasystems Inc.
US
Changing the value of the exposed column at the database level does not actually update anything about the case. The value needs to be updated in the blob through PRPC.
Pegasystems Inc.
IN
You should not change values for exposed columns in Database directly, As PRPC reads the values from BLOB. I believe you cannot alter the value of property in BLOB in Database directly. You should use PRPC only to alter the property values.
Cognizant
CA
Hi
Thanks a lot for the response. if the property is exposed, wouldn't the prpc take the value from exposed column.
or it takes the value from exposed column only for reporting. when a case is opened the value is still referred from BLOB.
Regards
Tarun
JPMorgan Chase & Company
US
Hi,
If you change the value in exposed column , pega application won't read the value while displaying and saving the object. The updated value will revert back when you try to save the work object.
So if you want to change the value in exposed column, open the work object by using OTTB methods, set the value to the property and save. This reflect both in exposed column and BLOB.