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?
Making fields conditionally required? Piece of cake! Events are the way to go for that. But populating a values list? That seems a bit too advanced for an event. I'm going to have to think about this one.
Generating email notifications is a pretty common use case for events, so I'm confident that's not the correct answer. This one's got me stumped though.
Oh come on, I thought we could delete records with events! That's like the first thing I learned about them. I'm going to have to really study up before the exam.
I disagree, I believe the answer is C) Make a field conditionally required because events are more about triggering actions, not enforcing field requirements.
Rosita
7 hours agoJunita
3 days agoLeonie
7 days agoShantell
13 days agoCecilia
15 days agoShantell
16 days ago