RFE – Enhancement to DeleteResourceEvent for Multi-Record Deletion Support in v9.0.0.2

Request Summary:

We would like to request an enhancement to the DeleteResourceEvent functionality in PRISM version v9.0.0.2 to better support multi-record deletion scenarios.

Current Behavior:

When implementing a DELETION trigger with the following configuration:

• Operation: PRE
• Event: delete.objects
• Trigger Type: ContentTypeMatch

We observe that the method event.getResourceIds() only returns the first resource ID when multiple records are selected for deletion (e.g., deleting 10 Loss Event records from the Grid View). The remaining resource IDs are not included in the list.

Expected Behavior:

We would expect event.getResourceIds() to return a complete list of all resource IDs selected for deletion in a single operation.

API Reference:

The API documentation for v9.0.0 provides two constructors for DeleteResourceEvent:

1. Single Resource Constructor:

public DeleteResourceEvent(Id resourceId, TriggerPositionType position, Context context)

1. Multiple Resource Constructor:

public DeleteResourceEvent(List<Id> resourceIds, TriggerPositionType position, Context context)

While the second constructor supports multiple resource IDs, it appears to be inaccessible or unsupported in the current DELETE trigger context.

Enhancement Request:

We request that IBM enhance the DeleteResourceEvent implementation to:

• Fully support the multi-resource constructor during Grid View deletions.
• Ensure event.getResourceIds() returns all selected resource IDs, not just the first.

This enhancement would significantly improve trigger handling for bulk operations and align with expected API behavior.

Thank you for considering this request.