Hi @SmrithiGo ,
Thank you for sharing the screenshots. They show that the Owner filter is using the DAM Property Predicate component:
Plain text
dam/gui/coral/components/admin/customsearch/searchpredicates/propertypredicate
The name property points to a field under jcr:content/metadata, and the text input is rendering in the Forms and Documents filter panel. This is consistent with the intended approach for allowing users to enter a custom String value.
The configuration also enables partialSearch and equalsIgnoreCase, indicating that partial, case-insensitive matching is intended. Please verify that the configured metadata path matches the property’s actual storage location and that searches return the expected results, including partial values and different letter cases. The screenshots confirm that the field renders, but not yet that the Forms search backend applies these settings correctly.
You can follow the same pattern for the other two properties once this behavior is confirmed. Keep the customization under /apps without modifying /libs, and validate it again on your target LTS release, particularly because the Forms console is reusing a DAM predicate component.
Thank you.