📊 Poll: What configurations would you like in the Search and Select pattern?

What are your top asks/improvements for the Pega Constellation Advanced Search? :magnifying_glass_tilted_left:
We are looking to gather feedback on the Constellation Advanced Search component to understand where we can improve the user and developer experience.

What enhancements would make the biggest impact on your projects? Vote below or drop your specific use cases in the comments!

Poll

  • Better support for Date Range filtering
  • Cascading / multiple search interaction (search once show results, search again to show less results)
  • Cross-data-type querying capabilities
  • Easier integration with External Data Sources
  • Enforcing constraints (Mandatory fields, Minimum characters)
  • More UI customization for Search Results (Row formatting, custom links)
  • Search results saved when navigating back to screen
  • “Show all” capability in search filters
  • Support for Reference Objects & Associations as search criteria
  • View selected items / Replay selected rows for confirmation
  • Other (Let me know in the comments!)
0 voters

Check out our docs and Constellation 101’s on the topic

Default date filters would be useful because they reduce effort and people love shortcuts. Examples: Last 24 hours, Last 7 days, Last 30 days, This month, and Previous month.

I wish to add Sort, Filters, Group By for Search and Select pattern.. This is a common requirement from Customers.

Disabling of selection based on custom condition

Could you tell me more?

  • Are you talking about a cascading filter? E.g. If i select United States as country, then the States would be US states?
  • Or do you mean some filters are disabled/hidden for some persona’s? E.g. only managers can search by “vip customer” flag?

The Reset action in the Search and Select/ (Advanced Search) control currently clears only the user-entered search parameters and does not reset the displayed results or selected records, as they are sourced from the data page. This behavior could be improved to align with traditional user expectations, where the Reset action clears both the search criteria and the displayed results/selections

Interesting one! I have not heard this before.

Just so I am clear, you want this button, to remove any selections in the table below?

And just so we delink the opinionated UI requirement from the outcome - we want a simple way to quickly remove selections? Would an ability to clear selection also meet this need?

I am just thinking, some use cases we have seen the desired to do multiple searches and multiple selections, so resetting search should not clear in that scenario.

Maybe it should be configurable, maybe it should be clearer - just trying to dive deeper into why you want the reset specifically? (otherwise @Kamil_Janeczek would not get his Uncovering the XY problem credits :wink: )

From a user perspective, when the Reset button is clicked, there is an expectation that everything is cleared — including search parameters, results, and any selected records.
At the same time, I understand that there are valid use cases where selections need to persist across multiple searches.

To accommodate both scenarios, we could consider either:

  • Making this behavior configurable, or

  • Providing a separate “Clear Results” option that removes all results and any selected records. (But providing a separate “Clear Results” option introduces an extra step for the user. They would first need to reset the search parameters and then click “Clear Results”, resulting in two separate actions.

    Wouldn’t it be more intuitive for the results to be cleared automatically when the search parameters are reset? Since the displayed results are generated based on the entered search criteria, once those criteria are cleared, continuing to display results from the previous search feels inconsistent with the current state of the search form.)
    For reference, please find the below link where the problem statement is explained with an example.

Reset should clear the entire search state, including filters, results, and selections, while making selection persistence configurable for use cases that require it.

Thanks for sharing your insight. This helps a lot.