Display list of child cases and a list(includes a page) under the Parent case

General
, ,
1

Tried creating a data page/List property sourcing this pagelist property which returns the list of child case and the list under it. Expectation is to show the list of child cases and under each child case, the lists of each case need to show in table. It would be better if each child case has a expand and collapse as count of child case is expected to be more like sometimes even in 50’s. In constellation, this property or data page is taken as query and not able to achieve the nest list view am looking for. Any suggestions would help.
Example:

ChildCase-1
Address 1 fields
Address 2 fields
Address 3 fields
Child case 2
Address 1 fields
Address 2 fields
Child case 3 and goes on….

1 Like
2

You can use Field group for your scenario.

In the exercise its products, in your scenario you can keep child cases. Then have child case details inside the field group.

3

@HaripriyaR17725451 If you’re building on 24.2 version and above, then you can choose Display as “Repeating View” to show cascading behavior in conjuction wtih Field Group (Expand/Collapse flexilbity)

1 Like
4

Thanks for responding @RameshSangili and @Anoop_Krishna . Issue here if the list type is query and not embedded data, then even if we use the repeating view, it doesn’t allow us to use the list on the view used in the repeating view. We will be able to achieve this in case of embedded data from a data table but here it’s all read only data that i have populated from child case and trying to show in Parent case.

5

Hello @HaripriyaR17725451. Welcome to the community. Are you trying to display this table in a form or in one of the summary tabs ?

For Summary Tabs

If you want this table in summary tabs, then you can make use of Insights.

For instance, I have this below structure and i want to display the Features list table in Release case summary tabs

  • Release
    • Feature
      • Story

Create an Insight on Feature class with grouping on Case ID and add whatever fields you want to display for the feature class.

Ensure that you have the pxCoverInsKey (Cover Object Key) field marked as relevant record and included as a primary field on Feature case type.

This will ensure that it will displayed in the Insight fields. Select this cover object key also as part of the display fields, so that you can use this to apply filter while you use the insight in Release case type.

image
image3220×1288 467 KB

Go to Release case type and include this saved insight in one of the summary tabs, and while you click on the gear icon, you will see an additional filter to apply.

Pass the Release case InsKey to map against the Feature Cover object key as shown below

image
image1000×580 30.1 KB

image
image1450×878 41.1 KB

Once you have the above configuration, then you should see an output like below

image
image2902×1246 256 KB

You can use this Insights only in summary tabs and not in Form views.

For Form and Partial Views

If you wanted to display the same table in a Form view, then you can follow below approach of creating a List view in parent case type.

Create a list view in Release case type and use the OOTB Feature list by Parent data page to get the Feature cases. Pass the instance handle key as the parameter to the data page.

image
image2786×1802 221 KB

Use CaseID as the group by field.

Now you can utilize this list view in either a form or summary tab. Choice is yours.

image
image2938×1216 389 KB

In both the above approaches, you will get the same table features. Choose which one suits better for you.

Hope this helps

Regards

JC

1 Like
6

Option One - Embedded data, can be shown as read only - so you can still use this type and still can use repeating view.

image
image447×404 11.5 KB

@Kamil_Janeczek goes through this solution in great detail in this Constellation 101

Option Two - List view/Insights I would be looking at a solution along the lines of @JayachandraSiddipeta’s suggestion. Using Insights or List Views - they give you a little more flexibility than perhaps the query field is giving you.

  • List Views can use gallery, but gallery can’t go multiple levels
  • However, both List Views and Insights can do multiple levels of groupings, which can turn flat data into something more hierarchical

These “report” options, have added benefits like searching and personalised views, which give flexibility to users depending on the “why” behind the need to show so many addresses and so many levels all at once (can get confusing)

Option Three - Case Hierarchy widget Infinity ‘25 introduced a case hierarchy widget. I don’t know the requirements behind showing all the addresses, personally I think option two is the most flexible but would be remiss to mention this option as viable. You can use this, along with Preview, to show a lot more data about each level. So depending on the “why” this might be a preferrable business outcome. I don’t have a screenshot of the widget + preview to hand, but it would work much the same as this example.

image
image1870×928 277 KB

@PierreM17643706 has a great write up in our Constellation 101 series on this

7

Hi @JayachandraSiddipeta , Thanks for taking time to give such a detailed explanation. This helps me to get the child cases in the parent case in table view. I am trying to get this in a form. I was able to achieve this table of child cases in the parent case instead of using the OOTB list view, I have created a data page that returns the child case details. Only addition I am looking for is also to display a list of details (page list available under the child case). When I expand the row of each child case id, I would like to see another table that displays table of the pagelist under each child case.

8

To extend the child case content display to show a table under each child case, you can make use of Preview/Open in new window. This will ensure that the Main table does not need too much of scrolling and expanding/collapsing.

As you have mentioned that the list of child cases would many in count, you can consider the preview approach to be a potential choice.

We cannot always have the same UI methodology which used to follow in traditional UI. Constellation needs the UI mind shift and choice of displaying the content in modern and efficient way.

To summarize, if you want a focused view of the nested child case table, you have three approaches

  1. Standard OOTB Preview
  2. Link column for each child case to open a modal window to view the table. For the link you might need to write a custom component for link to open a local action + view
  3. Focused preview with a custom component. Please take a look at the component developed for the same in the below link PDF viewer in a model window - Cosmos - #2 by JayachandraSiddipeta

I would suggest go for option 1

Regards

JC

2 Likes
9

@MarcCheong Option 2 and 3 are more like displaying the child cases and asking the users to navigate into the case using either Preview or open them to look into the more details which customer have already not happy with. They are very particular about showing the list of address under each child grouped by each child case and show in a form in the parent case. These details we are querying through a report definition and using a data page to bring them in the structure we want. To answer your option one, whenever using a data page or a pagelist with data page load, it becomes a query property not as embedded data in either table or repeating view which makes this implementation difficult for the result we want.

10

@HaripriyaR17725451 as @JayachandraSiddipeta has outlined very well, we can achieve the outcome you are after. Constellation is more prescriptive, in many cases for good reason (compared to UI Kit). The specific UI requirements you are trying to meet are not met by OOTB Constellation components or designs. This would likely be a a good opportunity to build your own DX Component, that meets exactly the UI the client is specifying. This would be the equivalent of building your own sections / action sets in the UI Kit world, giving you full control over what/when things happen using Pega’s Pcore/Pconnect API infrastructure.

We had a recent webinar on the topic, if you are unfamiliar. It might be good to start with one of the options mentioned earlier, achieving then business outcome and then implement a DX component as/when its ready, to achieve the UI requirements specified.

1 Like