What are your top asks/improvements for the Pega Constellation Advanced Search?
We are looking to gather feedback on the Constellation Advanced Search component to understand where we can improve the user and developer experience.
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.
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
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 @KamilJaneczek would not get his Uncovering the XY problem credits )
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.
Ability to Search outside of workobject (possibly landing page) → Open any result to display more info → Then initiating a workobject from the result info page. Had discussion with Richard Marsot during Pegaworld around this use case. Currently building a custom component for this.
Trying to get this to work for us at the moment, 2 things that are a bit of a struggle as follows:
The ability to delete selections from a view of the selected ones (as in Advanced Use Cases for Search and Select Pattern , see my picture). This is more of an issue when searching multiple times, as the first selection might not appear in your second search to unselect it, meaning you have to search it, to deselect it (or unselect ALL of your selections), which just isn’t very friendly.
The ability (in that same secondary view maybe) to enter some data, e.g. a quantity (maybe you have to select reference data copied to case for this?)
Item 1, yes, Search and Select is not designed for a Search/Select and Review with multiple searches layering on top of each other. We see that feedback throughout this thread, so good to get yours as well. I usually see a “review” of selected being on another step, say in a screenflow so you can confirm this is right.
Item 2. This should be embedded data. You would need to copy the data into the case but not via the checkbox I think you are referring. You should copy that data reference(s) into embedded data, so user can enter “quantity” and make other columns read only.
Would be great to have Search & Select pattern that supports displaying results as Cards instead of tables. For example, when search results return details along with an image, presenting them as cards would make the information more intuitive and visually appealing.
Having the flexibility to configure the results to be displayed either as a table or as cards, depending on the use case, would be a great nice-to-have feature.
)
