Yes, as these properties are used regularly by PRPC itself, e.g. for displaying the worklist, or for statistics on the dashboard. So these properties are already pre-exposed in the table and you do not need to optimise them yourself.
I am trying to Optimize a single value property in my work class. Because of large no of properties defined under work class, i am not able to see the desired property under Application class explorer, Pega 7 gave this new feature to show all results but clicking that opens all properties on the right panel, where in, i cannot right click my property and optimize it. How do i approach this.
All of the properties out of the box are exposed by Pega 7, meaning they all occupy a column in the resulting DB table. The only properties we need to expose are properties that we create to hold values in the cases we create. Both the Case ID and Purchase Order ID should be able to be looked up using the pxInsName property, you can find it on the pyWorkPage on the clipboard.
An example of a property that would need to be exposed would be, suppose we have a Candidate case and we want to figure out how many candidates are Married, Single, Divorced or Domestic Partnership. That property Marital Status is defined by us and as such the values are stored in the pzPVStream (or the blob). We would want to expose that property so we don't have to search the blob field for each record to find this information.