In Constellation there are different data access patterns. You have data references, queries, and also embedded data. Data references and queries point to data that lives outside the case. Embedded data is for data that lives inside the case and that you want to edit directly from within the case itself.
In Constellation, the user experience for these different types of data access patterns are different. For example, if you have a data reference in a table column, it will show up as a link and you can preview or open the referenced data object in a new tab to show more details about it.
However, if you wanted to show more details about a row in a list of embedded data, this was not easily achievable before Infinity '26. You had to perform some tricks to make a data reference point directly to embedded data. Not a great experience, and certainly not an intended or supported configuration.
What is new in '26
Infinity 26 brings the ability to show more details about an embedded table row by clicking the column value. Columns can be configured to “show additional details”, after which they will render as a clickable element.
How to configure
This configuration is supported for embedded lists shown as tables.
Start by creating or choosing an existing view in the object your embedded list points to. This view is the view that will show in a modal when you click the column value.
Then, navigate to the view containing your embedded list table. Drill into the table configuration. On the column you want to make clickable, open the configuration panel. You will see a new checkbox “Show additional details”. Check this, select “Open view”, and finally select the view you authored in your object.
Done! The next time you render the table, the column values will be clickable and launch the modal showing the view you configured.
Important note
The configuration checkbox “Show additional details” will only show up in a read only context. Meaning, the column needs to render as read only for this configuration to be available.
Some examples of when the configuration will -
show:
- The column is made read-only
- The table is added to a partial view
- The table is added to a form view as read-only
- The table is added to a form view as editable, but the edit mode is set to “edit in modal”
not show:
- The table is added to a form view as editable and the edit mode is set to “table rows” (inline editing)
Bonus tips
- This feature can be “nested”. Meaning, if you show a nested embedded list in the “show additional details” view, you can make the columns in the nested list clickable as well. In the UI, this would manifest as another modal that shows on top of the first modal.
- While the main idea behind this feature is to show more details about the row than can fit into the table columns, there is nothing that prevents you from configuring the “additional details”-view with other things. For example, if I have a list of counter parties: In my details view I might add a query property that fetches all the accounts that counter party has. So this feature is quite flexible when it comes to what kind of details you want to show to your users in the modal(s).
To consider
Remember that you still need to carefully design your data model and your data access patterns. The fact that you now have more flexibility in how you can present embedded data in the UI, does not mean that everything should now be embedded data. The core principle that the Constellation design system forces you to think about your data model, still applies.
For situations where embedded data does make sense, this enhancement in Infinity '26 is certainly a welcome one!
Recap and key details
- The configuration is made on individual columns in embedded data table views.
- The configuration option will only show in a read only context. Editable columns will not surface the configuration option.
- You can nest this feature to show modals on top of modals should you need to.
- Remember that the core Constellation data model design thinking still applies. This feature should not be used as a way to bypass proper data model and data access design.
Implementation video
Watch the video (2 minutes) →
Documentation
Release notes for the feature: Pegasystems Documentation
Enjoyed this article?
See suggested articles from our Constellation 101 series and view all our Knowledge Shares from our User Experience Expert Circle.