Conversation
adept view
IN
Last activity: 2 Sep 2025 13:11 EDT
Bulk Action Required for Data Records
We would like to understand the best recommended approach for handling bulk actions on data records (for example, bulk delete) within Constellation.
Consider a scenario where a list of data instances is displayed on a screen, and each row includes a checkbox. Users should be able to select multiple records, and once selected, relevant bulk processing options (such as delete or hide) should be presented on the same screen.
Currently, the OOTB CRUD functionality supports only singleton operations. What would be the suggested approach to extend this for bulk operations in Constellation?
Please note, our requirement is to handle this from a non-case context.
We would appreciate your guidance.
Pegasystems Inc.
GB
@Unnikrishnan T Nas you've rightly pointed out, Bulk Actions, only exist within the context of cases.
- https://docs.pega.com/bundle/platform/page/platform/case-management/bul…
- https://docs.pega.com/bundle/platform/page/platform/user-experience/set…
If you wanted to leverage a Constellation OOTB portal, then using cases or a case would be the only way to do this. I know it's not your preferred implementation, but it adds the benefit of an audit trail, which CRUD actions on data does not. When you start working in bulk, there tends to be traceability requirements as you can do more damage in bulk...
Extending Constellation UI
Obviously, that changes if you choose to extend constellation with your own DX Component or SDK front end, but that would be far more complex work. Including the need for calling each API for the data instances and error handling.
Delegated Data Portal
If you must bulk edit, then you might consider using App Studio or bringing back data delegation. This has its own drawbacks but is feasible in Constellation Applications.
@Unnikrishnan T Nas you've rightly pointed out, Bulk Actions, only exist within the context of cases.
- https://docs.pega.com/bundle/platform/page/platform/case-management/bul…
- https://docs.pega.com/bundle/platform/page/platform/user-experience/set…
If you wanted to leverage a Constellation OOTB portal, then using cases or a case would be the only way to do this. I know it's not your preferred implementation, but it adds the benefit of an audit trail, which CRUD actions on data does not. When you start working in bulk, there tends to be traceability requirements as you can do more damage in bulk...
Extending Constellation UI
Obviously, that changes if you choose to extend constellation with your own DX Component or SDK front end, but that would be far more complex work. Including the need for calling each API for the data instances and error handling.
Delegated Data Portal
If you must bulk edit, then you might consider using App Studio or bringing back data delegation. This has its own drawbacks but is feasible in Constellation Applications.
- https://docs.pega.com/bundle/platform/page/platform/user-experience/lau…
- https://docs.pega.com/bundle/platform/page/platform/data-integration/de…
Future
This is on the backlog for our product (EPIC-97909 and EPIC-106913) but I don't see this coming in for Infinity '25 so you'd need to explore other options as outlined above if there is a short term need.