Question
Red Alpha
US
Last activity: 28 Apr 2025 11:51 EDT
Adding Custom Actions to an Embedded Data table
Hello Everyone! My team and I have a use case wherein we would like to see if it would be possible to expose a custom action on an Embedded Data table in addition to the OOTB "Edit" and "Delete" actions. My team and I are working on a case type which includes an embedded data field; which is intended to contain a list of statements. We display this embedded data list as a table on a view in our workflow and were curious if folks are having any luck exposing table row actions in addition to "Edit" and "Delete". Would very much appreciate any thoughts!
Pegasystems Inc.
US
@TessPorter instead of using Embedded Data, do you think you might be able to create a dedicated Data Object representing statements? This would allow you to make use of Create Case Actions:
In case you need someone to edit transactions manually, you could simply enable CRUD for your Transactions Data Object.
Red Alpha
US
@mrwolf Thank you for your response! Yes, we've implemented a dedicated Data Object to represent statements and their component parts. This Data Object is referenced in the configuration of the Embedded Data field in our case type. The additional actions we're hoping to implement are less CRUD focused. If possible we would like to expose an action in addition to the OOTB Edit and Delete functionalities that would allow us to launch a different view in a modal.
Pegasystems Inc.
US
@TessPorter thanks for clarifying! I don't believe Actions will be supported for Embedded data objects - you would have to work with data reference fields.
So you might be able to restructure your app to have data object representing individual transactions (instead of storing them on the work object, which embedded data technically does). This would allow you to actions right out of the box - and they don't have to be CRUD focused at all! You could, for example, think of a case type named "Investigate Possible Fraud" that gets kicked off for a particular transaction. Users would be able to start that case directly from a table showing relevant transactions on any landing page, Pega would then automatically create a new case, passing the reference to respective transaction.
