Why is updating pyStatusWork doesnt resolve the case?
I have some "m" number of cases to be resolved in the same time. To improve performance i simply do a RDB save of all those cases by changing pyStatusWork property to "Resolved-Completed". But when I do a obj-open by handle of the case, in the case page I don't see them resolved though the pyStatusWork column has the resolved status updated in DB.
If you are doing an RDB-Save and just updating the exposed column, the value would not get propagated to the blob column. You would need to open the work objects instead and update the status. When the blob column is updated, the exposed column will also be updated.
Yes I agree its useful for reporting. But in this process if i do RDB-save and updated the exposed columns alone, then there would be different values in Blob and exposed columns. So this will provide discrepancy between the report data and actual work object. Will this not cause an issue to data integrity?
As per Pega architecture when to update any optimized property in BLOB column such as Obj- methods, it will also updated the respective exposed column of that property but vice versa is not true. Here you are updating the exposed column using RDB save method, so the change is not propagating to the pyWorkStatus in BLOB column.
Most of the time we optimize/Expose any property to use it for reporting purpose. So that Pega don't have to open the whole BLOB just to fetch few properties values. Opening whole BLOB a performance consuming process and may make your reporting process significantly slow. That's why Pega is recommending as best practice to expose field column (Not filter column) which are suppose to be used in Report Definition or Obj-Browse method though we can fetch the data without exposing them .
Hope you get the sufficient clarification. Please mark the answer accordingly.
How would you Resolve the case from an activity or in the flow. My situation is that as soon as that case is created and some data is stored, i should resolve it immediately within same flow transaction.
Thank you for posting your query in the PSC. This looks like an inactive post and hence, we suggest you create a new post for your query. Click on the Write Post button here. Once created, please reply back here with the URL of the new post.
You may also refer this discussion link as a reference in the new thread.