We have a requirement to implement an Organization Search in Pega Constellation similar to the functionality available in the Traditional UI.
Traditional UI behavior
The user clicks the Search icon next to the Organization field.
A popup (Local Action) opens.
The user enters address details (such as Street, City, State, ZIP, etc.) and performs a search.
A list of organizations matching the entered address is displayed.
Since multiple organizations can have the same name but different addresses, the user selects the appropriate organization from the list.
After submitting the selection, the chosen organization and its address details are populated back into the main screen.
Requirement in Constellation
We need to achieve the same business functionality in Constellation, where users can search organizations by address, choose the correct organization from the results, and have the selected organization populated back into the main screen.
Questions
Is there an out-of-the-box way in Constellation to display both the Organization Name and Address in the search results, similar to how the Owner reference displays both Name and Email?
What is the recommended Constellation approach to implement this requirement?
Are there any out-of-the-box patterns or best practices to achieve this functionality without building a custom DX component?
Any suggestions or implementation approaches would be greatly appreciated.
Yes, this can usually be implemented with the OOTB Constellation Search and Select pattern, without building a custom DX component. The closest design is a single-record Data reference to an Organisation data object, configured to display search results in a table rather than using a simple autocomplete.
The Constellation Search and Select pattern is intended for this type of use case: the user searches using configured fields, sees matching records in a table and selects one record. Because the results are displayed as a table, you can show the address columns alongside the organization name, which solves the duplicate-name problem.
The Organization list source can be a data page or query that calls the external REST service. The query should accept the configured search values and return a normalised Organisation result containing both the organisation id and address information. If the source is external, I would avoid exposing the raw integration structure directly to the UI. Instead use a concrete Organisation data object or wrapper response that gives Constellation a stable list/single-record contract
A custom component should be considered only if the requirement needs a fully customized modal/search interaction that cannot be represented by the Data reference configuration.
Though that is based on Infinity '24, in Infinity '26 it has even more capabilities, so would urge to check out the latest release notes
And there are a handful of dedicated Search and Select knowledge shares, on different extensions and customizations people have shared in our Constellation 101 series.