Filtering by status works in /activities API but not in resource route — is this expected?

Summary:

Hi Community,

I’m currently working with Oracle Field Service REST APIs using Postman to test endpoints.

I noticed a difference in how filtering behaves between these two APIs:

✅ GET /rest/ofscCore/v1/activities

This endpoint supports filtering via the q parameter. For example, the following works perfectly in Postman:

q=status == 'completed'

It correctly returns only completed activities.

❌ GET /rest/ofscCore/v1/resources/{resourceId}/routes/{date}

When I try the same filter here:

q=status == 'pending'

The response still includes all activities for the resource on that date, regardless of their status. It seems the q parameter is ignored.