Events can be used to trigger a number of different layout effects, based on a user's interaction with other fields in the application. Which of the following actions CANNOT be triggered by an Event?

Deleting a record is a destructive data-layer operation that falls outside the scope of what Events are designed to do; Events are scoped to layout effects and notifications that respond to user field interactions within the form. The platform restricts record deletion to explicit user actions or scheduled data management processes, not event-driven field interactions.

Generating an email notification is a supported Event action that can be triggered based on a user's interaction with a field.

Making a field conditionally required is a valid layout effect that Events can activate in response to changes in other fields.

Populating a values list with a value selected in another field is a supported Event-driven behavior for dynamic field control.