Newly added property is not appearing when open the work object.
Hi Team,
I have requirement to add a new property to the work table and it should be available for reports, so a new property was created in work class and it is manually added to the work table via alter SQL querty. For the existing resolved work objects the data patch was done through update SQL, since resolved objects cannot be updated from PEGA with out re-opening.
Report are working as expected based on the newly added property but when a existing case is opened (review / re-open) the property was not appearing on pyWorkPage, however it is working as expected for newly created work objects.
Expecting a prompt response. Thank you.
Accepted Solution
Updated: 19 Apr 2016 2:55 EDT
Process 360
IN
The following is my assumption.
It is working for reports because the value is being fetched from the exposed column to populate in the report where as WO is concerned Pega will make use of blob to open the object on to the clipboard which doesn't have the updated value updated via sql.
Write an activity to loop all the WO's : do a obj-open-by-handle --> Property-Set --->Obj-save and finally commit. this way both the blob and exposed column will be in sync.
Updated: 14 Apr 2016 0:33 EDT
Pegasystems Inc.
US
Hi Satish,
The ideal way of achieving your requirement should be like below -
1. Create a property in work class as per your requirement.
2. Optimize the property using Optimization Wizard, so that a new column gets created in DB for the corresponding work table.
3. The newly added property will not be shown in pyWorkPage of Re-Opened cases, unless until it is referenced in case flows.
Since we are adding a new property all to gether, and in case of no DB updates for this column, the value would be null if you reference it in reopened cases.
Optus
AU
Hi Harish,
Thanks for the swift response.
Can you please elaborate on Point(3), I want the newly created property to persist on pyWorkPage when an existing case was opened / re-opened.
Note: I have already stored the value for the newly created property for resolved work objects via SQL.
Accepted Solution
Updated: 19 Apr 2016 2:55 EDT
Process 360
IN
The following is my assumption.
It is working for reports because the value is being fetched from the exposed column to populate in the report where as WO is concerned Pega will make use of blob to open the object on to the clipboard which doesn't have the updated value updated via sql.
Write an activity to loop all the WO's : do a obj-open-by-handle --> Property-Set --->Obj-save and finally commit. this way both the blob and exposed column will be in sync.
Optus
AU
Hi Bhanu,
Thanks for the response. Commit not happening from PEGA but how ever Obj-Save with "WirteNow" and "WithErrors" check boxes checkd fixed the issue.