Succeed Insurance has a page in PolicyCenter with a large fleet of vehicles.

When dealing with alarge fleet of vehicles, performance is the primary concern. Retrieving thousands of vehicle records and filtering them in the application server's memory (Options E and F) is a high-risk anti-pattern that leads to latency and high memory consumption.

The best practice for implementing efficient UI filters on large datasets is to useGosu Standard Query Filters(Option C). These filters are added to the ListView's toolbar. When a user selects a filter (e.g., "Only Heavy Trucks"), the Guidewire platform translates that filter into a SQL WHERE clause. This allows thedatabaseto do the work, returning only the specific subset of vehicles requested. This "Database-First" approach ensures that the application server remains responsive and that the network traffic between the database and the application is kept to a minimum.

Option A (filtering on the Row Iterator) and Option B (using "visible" properties) still require the system to fetch all the data from the database first, which does not solve the underlying performance issue. Using Query Filters is the only scalable solution for InsuranceSuite applications managing high-volume data.