We are implementing a search requirement with advanced search and select pattern in Pega Constellation. We included the Search component in Screen flow as business wants perform search and based on search results, the next screen will be populated. We are searching with couple of Search attributes and in case if there are NO results , then we need to pass those values entered in search attributes to next screen in flow and populate them in the respective fields.
We tried different approaches but none of them worked. Is there a way to pass the search attribute values entered in the search fields to next screen?
Alternative 1: During your search, you can add 1 item which stores all search properties. If the user than selects that one, you can copy the properties back into the fields required
Alternative 2: use the properties on case-level which are used as input of your DP for searching.
Alternative 3: in the search DP, add logic to store the search criteria and later retrieve the last one if the ID of the selected item is empty.
There are of course downsides to all of them, you need to pick the one which suits your need
The Search and Select form uses a transient container to build the search interface. Because the container is transient, the associated fields do not participate in the main case payload, and therefore you won’t have access to them for later use in the case. Personally, I would be exploring what Ronald suggested as OOTB alternatives
Customize your own DX Component
However, we recently posted a Constellation 101 article that covers how to customize this. It is not low code, so I would still recommend caution - it is however, an option, if this is a 100% must have despite all the usual caveats. I’d recommend checking out our 101 series, we have a couple others on this feature and ones you might also be interested in.