In our Constellation application, we have multiple case types and several Insights, with some Insights being specific to certain case types.
We are planning to introduce a dropdown for case type selection, and based on the selected case type, another dropdown for Insights. Depending on this combination, the relevant Insight will be displayed.
We would like to know if it is possible to customize the Explore Data page to support this behavior. If not, we may need to create a new landing page. However, we are unsure how to design a view that includes both dropdown selections and Insights on a landing page.
Any suggestions or guidance on this approach would be greatly appreciated.
I would not recommend customizing the OOTB Explore Data page for this requirement. Explore Data is intended as the standard landing page for creating and exploring Insights, whereas your use case sounds more like a guided business dashboard.
The cleaner approach would be to build a custom landing page in Constellation with two dropdowns one for Case Type and one for Insight and use visibility conditions or dashboard-style filtering to show the relevant Insight based on the selected combination.
If the main driver is Case Type, you could also look at dashboards with promoted filters or cascading Insight filters in v25 which may reduce the need to build every permutation manually.
I wouldn’t recommend to customize the OOTB Explore Data. Explore Data has a filter option to drill down to specific case type. You can also use Search icon to filter the respective insights for each case type.
Other alternative option is to create the Landing page as @RaviChandra suggested. However, the security restrictions needs to be applied and modifications can’t be performed from Landing page (to add/modify the columns)
@AbhilashK2788 If the landing page is configured as a Table/List page, then it is mainly designed to show the table and its built-in filtering options. It is not the right format for placing arbitrary dropdown controls above the table.
For this requirement, the better approach is to create a custom landing page (for example, a one-column landing page), place a small view with the dropdown fields at the top, and then show the relevant table or Insight below it. That aligns better with how Constellation landing pages are intended to be composed.
If the dropdowns are only meant to filter the table data, first check whether the built-in landing-page table filters can handle the use case before building a custom selector view.
