We are running an application on Pega Platform 7.2.1 utilizing both a Framework layer and an Implementation layer.

We defined a report definition in one of our work classes in the implementation layer and noticed a weird behaviour with the "Report on descendant class instances" settings:

1. If we do not select "Report on descendant class instances" (we don't have descendants for this class), the query adds a filter on pxObjClass using like operator (e.g. pxObjClass like 'MyApp-Work-MyCase%') as if it tries to look also for descendants
2. If we select "Report on descendant class instances" and "Include Implementation class only" (our class is the implementation class) we get the same behaviour as point 1
3. If we select "Report on descendant class instances" and "Include all descendant classes" (as said before, we don't have descendants for this class) we get the filter using the equals operator (e.g. pxObjClass ='MyApp-Work-MyCase')

The results set is the same for the 3 settings, but we get performance issue using 1 or 2, because the like operator for PC0.pxObjClass is repeated for each join and association.

As per documentation, it seems that the system is behaving the opposite as expected:

Is there any bug in this Pega version that was fixed in newer versions or that could be fixed installing any hotfix?