We would like to seek your guidance on the recommended approach for handling bulk actions in general scenarios where large volumes of data are displayed in a Constellation screen during case processing.
For example, consider a grid with a significant amount of data loaded for quality verification. In cases where low-quality records are identified, we may need to perform bulk operations such as deletion or bulk updates to certain fields with specific values. We are looking for the suggested mechanism to efficiently process such bulk actions within the grid. (Here, the grid is part of the screen built using the data reference pattern, along with other data elements that may or may not be related to this scenario.)
If the intent is to allow processing within the same screen and reflect the updated values immediately, rather than only upon submission, are there any options available to achieve this?
In particular, for common bulk actions like delete or bulk update, is there a recommended best practice? If the expectation is that such processing should only occur on submission, then the entire screen may need to be dedicated for this purpose.
@Unnikrishnan T N answered some of this on your previous post on Bulk Action Required for Data Records. Wrapping your processing and bulk actions inside a case is the right way to go. For me it gives you more flexibility to show, select, update, replay and approve the updates - functionality you can’t do in CRUD actions on data. If you go this route, changes aren’t designed to be done instantly, it would normally happen on Submit via a Saveable Datapage (save plan).
This document might help give you some ideas on ways you could do this yourself. Basic premise is Data Reference, Saveable Datapage, even to trigger save plan for Saveable Datapage. As you can see from this, its done post submission as you don’t have any hooks in the UI for on change save. Even if you did, I wouldn’t recommend it as it wouldn’t allow for user error and “undo” the changes they made.
