The ProductQueryService in its current form splits product selection into a database part and a subsequent in-memory part. This is OK for selection policies returning a number of products, but may fail to find suitable products in the case of "Latest..." policies, e. g. LatestValidity: The database query will provide the product with the latest absolute validity, but thereafter this product may be rejected, because it does not fulfil the input filter conditions specified in the processing order.
This behaviour must be changed to always determine the products using a relative "Latest..." selection strategy, which filters by input condition first, and selects the products fulfilling the selection policy afterwards.
The ProductQueryService in its current form splits product selection into a database part and a subsequent in-memory part. This is OK for selection policies returning a number of products, but may fail to find suitable products in the case of "Latest..." policies, e. g. LatestValidity: The database query will provide the product with the latest absolute validity, but thereafter this product may be rejected, because it does not fulfil the input filter conditions specified in the processing order.
This behaviour must be changed to always determine the products using a relative "Latest..." selection strategy, which filters by input condition first, and selects the products fulfilling the selection policy afterwards.