We have a requirement where in we need to let users input few values and provide an option to search, On click of Search there should an API call made and the fetched results to be shown to the user.
@Hari krishna a good question. I would suggest reframing the question slightly to focus on the business outcome “I need to be able to find the right [data instance] to view”. This can help think of it in terms of the centre-out model that is required to allow Constellation to achieve this.
To author this outcome you need:
data object, that is stored on an external system of record
a landing page
a List View or Insight focused on the data object
Promoted filters on that List View / Insight
A few good articles from our Constellation 101 series that can help here - i’ve bolded the 2 most important for your use case (in my opinion):
@Kamil Janeczek @MarcCheong. Thank you for your inputs.
The business requirement is, we need to be able to see the number of cases created in XY application (XY application is not built on Pega) based on the given criterion.
I should be able to search the cases based on A,B,C… parameters passed. This option should be available on Landing pages (Not under any case context).
@Hari krishna this is possible yes, the focus is getting the data object built and using promoted filters to do the search.
Natively this will return results before the filters are input but there is an article i shared where you can return 0 results until the filters are selected. You just have to be conscious of the UX implications of that as its not natively what the Constellation component was designed for.
Hi @MarcCheong Thank you for your inputs, but the application that we are trying to get results is not a Pega Application. Can you please advise if we can build search screen in this scenario as well.
If the approach in this is followed, it should be possible for any application. You just need to configure the connect REST according to the API provided by the other application. I am not completely sure about the longevity of the approach in the link, as it uses properties from clipboard to map the search filters to the connector that may change in future if Pega changes the architecture of the component. But, as of now it seems as a viable option for the requirement you have.