Hard to succinctly sum this up in the subject line, but here is some context:
Context: this is about editable fields on a CTA layout where you can add columns to search by, and filters and filter logic to control the results that can be returned:
In this example I have a field I’ve added to the CTA. I have a few searchable fields, and a number of filters and some advanced logic.
The Problem: The filter criteria and logic only apply AFTER the CTA has been fully created. During the process of CTA creation, end-users could search for anything even if it doesn’t match the filter logic applied to the search. Only after creating the CTA and returning to it would the criteria apply.
Consider the existing workflow now:
- Admin sets up search criteria to curate results
- End-User starts to make a CTA
- Because the results during CTA creation are not curated, end-users at this stage may enter something in that may or may not be correct OR they will have to:
- Save the CTA
- Return to/reopen the newly created CTA
- Search/input the now curated info into the field search.
VS the ideal state.
- Admin sets up search criteria to curate results
- End-User starts to make a CTA
- End-User searches via the curated list and can create the CTA successfully.
Desired Outcome: Have search filter criteria honored during the creation process of the CTA, not just once it is fully created.
This likely isn’t an issue just with CTAs, but this type of behavior really adds a burden to the end-users by adding extra steps, or by negating this configurability altogether by allowing the search criteria to so easily be circumvented.
I understand that this is currently as designed, because the CTAs aren’t created yet, but this seems like a basic need for any manually created CTA.
