Currently, we cannot display the further transaction information using a Modal or hover option in a data view table when click on a specific column. As per our investigations constellation design patterns seems to be supported the modal-based approach only when the transaction data is stored as a Pega data instance (for example, in a data page backed by persisted records).
In our case, the transactions are loaded dynamically via APIs and exist only at runtime. When a modal or link is triggered, Constellation attempts to open the transaction as an object instance using Obj-Open-By-Handle. Since these transactions do not persist as instances in Pega, the system cannot locate them, which results in an error.
Because of this architectural limitation, the modal or hover interaction is not supported for API-sourced, non-persisted transaction data in Constellation at this time.
(Note: This behavior was observed in the Smart Dispute agentic automation initial transaction search screen.)
We are using the OOTB Search and Select template. Once the transactions are loaded into the table and the user clicks on the Merchant Name, the system is expected to load the remaining transaction details in the Balances Modal. The OOTB Balances view already contains several of these additional attributes from the Transaction entity.
This issue started occurring after the API was integrated to load the transactions. When the same transactions are persisted in the CDM tables, this issue does not occur.
You have to maintain/implement the single lookup record data page as well, which accepts a unique id as parameter and check the “Is this page used for alternate key storage“ option and provide the linked field.
A data transform which calls the service again to fetch the list of records and then using the key you have you can filter the record and set it to primary page.
A connect rule to the service passing the unique id you have and get the data directly from service for that one record.
Good catch @JayachandraSiddipeta we almost always need both data pages single mode and list mode. This is visible on first glance and is cause of typical issues.
To my knowledge this feature (Open View - which is not a hover but a click event) only exists on Case Types, not on Data Types. Case types are normally stored in Pega and have limited integration capabilities. However I assume you use CDM which uses a hybrid object called Entity at the moment (combining Data and Work related features). Just like the other option “Link to object“ (which is available in bot Data and Case Types), this feature only works if you have setup the single page datapage with the right parameters to fetch the details from the source (external or internal should not matter).
I worked on a similar case not too long ago, and your assessment is consistent with what we observed. As @schos1 pointed out, the Open in View capability is only available for cases and does not apply to data types, because it is dependent on the presence of a valid pzInsKey.
When data is sourced from an external API and exists only at runtime, no pzInsKey is available, so Constellation cannot open an instance and resolve the target view or modal.
Based on that earlier investigation, an enhancement was raised to consider for a future release.
FDBK‑134688 – Support ‘Open in View’ for External Data Sources.
