I’m submitting this enhancement idea on behalf of our strategic client Optum and the Optum Insight BU.
Overview
• Optum would like Response Projects to provide the same dynamic filter option behavior currently available through Content Library Facets Search.
• When a user selects a Collection, Custom Field value, Tag, Response Header, or another supported filter, subsequent filter lists should dynamically update to display only the options that are applicable to the filters already selected.
• This behavior should apply across Response Projects Ask, AI Assistant, AI Draft, and Recommendation Engine, including both AI and non-AI project filtering configurations.
• The applicable options should be dynamically evaluated as filters are being configured, before the user selects the Apply button.
Current Challenge
• Optum has hundreds of Tags, Collections, Custom Field values, and other configured filter options.
• Today, when users configure Response Project filters, the selection list displays every configured option, including many values that have no relationship to the filters already selected.
• Users must scroll through lengthy lists and manually determine which options are applicable to their previous selections, creating significant time consumption and frustration for project teams.
• The current behavior can present filter options that are known to have no applicable records based on the filters already selected.
• For example, currently when a Collection contains only documents and no Response Headers, selecting that Collection will result in no Response Header options being presented via the “No Options” pop-up, rather than displaying all configured Response Headers.
• Similarly, if a selected Collection contains no records associated with a particular Custom Field, the corresponding Custom Field filter should display a message such as “No Options” rather than presenting every value configured in Org Settings.
Proposed Enhancement
• Apply the same dynamic filter elimination logic used by Content Library Facets Search to all applicable Response Project filtering experiences.
• As each supported filter is selected, dynamically evaluate the remaining filter options against the records applicable to the filters already entered.
• Subsequent filter lists should display only values that are applicable to the previously selected filters, regardless of which filter type was selected first.
• The filtering logic should work before the Apply button is selected so users receive an immediately relevant list while configuring their search criteria.
• This behavior should apply when configuring project filters from Ask, AI Assistant, AI Draft, and Recommendation Engine, including Project Settings, (both AI and non-AI project setting configurations).
• The behavior should work across Collections, Tags, Custom Fields, Response Headers, and all other supported filter types.
• If no options remain applicable based on the filters already selected, the filter should display “No Options.”
Expected Impact
• Reduce the time required to configure Response Project searches and filtering criteria.
• Eliminate unnecessary scrolling through hundreds of irrelevant Tags, Collections, Custom Field values, and other configured options.
• Improve the user experience by presenting only meaningful and actionable filter selections.
• Provide consistent filter behavior across Content Library Facet Search and Response Projects.
• Reduce configuration errors and the likelihood that users select filters that produce no relevant results.
• Improve scalability for organizations with large and complex content taxonomies, extensive tagging structures, numerous Collections, and large numbers of Custom Field values.
• Increase confidence in Ask, AI Assistant, AI Draft, and Recommendation Engine searches by ensuring that available filter options accurately reflect the content available under the filters already selected.
• Establish a more intuitive and efficient filtering experience by dynamically narrowing available choices as users progressively define their search criteria.
Screenshot Examples Below:
Thank you to the Product Team for your time and consideration. Please reach out if any further clarification is needed.
@Gosia Rios for visibility.
