Notifications and Scheduled Jobs
Notifications (sysevent_email_action) send email (or other channels) based on events or conditions. Candidates must understand events (sysevent), event registry, notification triggers (record inserted/updated, event fired), recipients (users, groups, fields), and notification conditions. Email templates and mail scripts format content. Scheduled jobs (sys_trigger) run scripts or flows on a cadence (daily, weekly, cron). Scheduled flows are the Flow Designer equivalent.
Know the difference between event-driven notifications (fired by gs.eventQueue) and condition-based notifications (evaluated on record change). Understand notification preferences (users can opt out) and email logs for troubleshooting. SLA breaches can fire events that trigger notifications.
Traps: assuming a notification fires for every update (conditions and triggers gate it). Assuming gs.eventQueue sends email directly (it fires an event; a notification must be registered to act on it). And confusing scheduled jobs (server-side scripts) with scheduled reports (email report output). Another trap: forgetting that notifications respect user preferences and can be suppressed.
Worked example: To notify an assignment group when a high-priority incident is created, create a notification with trigger record inserted, condition Priority is 1 - Critical, and recipients set to the Assignment group field. Alternatively, fire a custom event with gs.eventQueue('x_acme.critical_incident', current) and register a notification on that event.