Skip to main content
Discovery

Fields on CTA Should Honor Search Criteria

Related products:CS Cockpit & Playbooks
anirbandutta
Sebastian
FMEEvangelist
  • anirbandutta
    anirbandutta
  • Sebastian
    Sebastian
  • FMEEvangelist
    FMEEvangelist

bradley

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:

Example for context

 

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:

  1. Admin sets up search criteria to curate results
  2. End-User starts to make a CTA
  3. 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:
  4. Save the CTA
  5. Return to/reopen the newly created CTA
  6. Search/input the now curated info into the field search.

VS the ideal state.

  1. Admin sets up search criteria to curate results
  2. End-User starts to make a CTA
  3. 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.

 

7 replies

benwanlessmenlo
Forum|alt.badge.img+4
  • Contributor ⭐️⭐️⭐️⭐️⭐️
  • 115 replies
  • August 15, 2023

Also, This feature would be great to extend to ALL Lookup fields.

It is great in CTAs it would be great in other objects as well!

 

Please consider this!

 

Best,

Ben Wanless


bradley
Forum|alt.badge.img+7
  • Author
  • Expert ⭐️
  • 1126 replies
  • June 26, 2024

@revathimenon any chance we can get some 👀 on this?


revathimenon
Forum|alt.badge.img+6
  • Gainsight Community Manager
  • 565 replies
  • June 26, 2024

Sure @bradley, let me get some PM eyes on this.


mpatra
Forum|alt.badge.img
  • Gainsight Employee ⭐️
  • 137 replies
  • June 26, 2024

Hi @bradley ,

 

This is a technical limitation we have with our platform. I will have some discussion on this with the architects and get back to this group.

Thanks,

Monica


mpatra
Forum|alt.badge.img
  • Gainsight Employee ⭐️
  • 137 replies
  • June 26, 2024
New IdeaDiscovery

bradley
Forum|alt.badge.img+7
  • Author
  • Expert ⭐️
  • 1126 replies
  • June 27, 2024
mpatra wrote:

Hi @bradley ,

 

This is a technical limitation we have with our platform. I will have some discussion on this with the architects and get back to this group.

Thanks,

Monica

Interesting - my understanding was that this was actually an intentional move at one point, not based on a technical problem. Hopefully this is something that can be updated. As it stands, there is almost no point to configuring this because it is so unintuitive and cumbersome for end users.


bradley
Forum|alt.badge.img+7
  • Author
  • Expert ⭐️
  • 1126 replies
  • July 16, 2024

This one is out here too for some reason 

 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings