We have a report definition in which Caseid is not displayed in one column and clicking on it would open that particular work item. There is a scenario where case id for a particular case is blank and when u click on that blank space it opens a work item which doesn't have a case id. We tried to reproduce this issue by making pyid=null. This only created a blank space for that particular case in report but when that blank space was clicked it opened that work item and that workitem had the case id.(according to the issue ,when they opened caseid was not shown ) so , Can anyone suggest ur views/approach to trace the issue regarding this ?
If you are on Pega7 and if you have configured the Report Definition in Repeating grid. Then you can add conditional action (if the condition is met, then only the action would be taken) For each action there you can specify a condition.
If your work table has a BLOB and even if you make the pyID exposed column as NULL, the value is not removed from BLOB. Thus when you open up the work object by clicking on the row, it will show the pyID from the BLOB as Obj-Open gets everything from the BLOB.
Are you sometimes working with temporary WorkObjects on your application ? I have seen a situation in the past where the temporary flag was unfortunately deleted and the system was trying to persist the WorkObject on the database without having any ID been generated.
If there is no missing pyID, then the only possibility of any work object without pyID is that there has been certain maintenance operation performed using an activity, which may backed up an existing work object, but forgot to delete the backup.
Looking at the case data (for the case with blank pyid) as well as case history (and assignments if the case is in-flight) might give you more insight into the issue. Also consider any additional processing that happens on your cases. And I'll also look at the case that have matching pxCreateDateTime and compare the case data with that of the case with blank pyID.