When configuring the content of an Email Notification, which syntax should be used to reference the properties of an event triggering the Notification?

When a notification is generated from a platform event (raised with gs.eventQueue / gs.eventQueueScheduled), the only accessible data are the event’s own fields: name, parm1, parm2, etc. Inside the notification template these are referenced with the variable prefix event, using Jelly syntax ${event.field}. Therefore ${event. } is the required pattern. Other prefixes address different objects (current record, GlideSystem, etc.) and are not resolved for event-driven notifications.

B. ${current. } – current refers to the GlideRecord that triggered a record-based notification, not to an independently queued event; it is undefined for event notifications.
C. ${property name>.getDisplayValue()} – malformed Jelly; no object prefix or closing brace, and getDisplayValue() only works inside blocks, not inline placeholders.
D. ${gs.} – gs is available only in scripted sections (), not as a placeholder; inline resolution with ${gs.} is unsupported.

1. ServiceNow Documentation – “Using variables in notifications”, Tokyo release, section “Event variables”, para 1: “Use ${event.variablename} to reference event fields such as parm1, parm2.”

2. ServiceNow Documentation – “Create an email notification for an event”, Tokyo, Step 8 note: “In the message body you can access event parameters by typing ${event.parm1} …”

3. ServiceNow Developer Site – “Events and notifications”, sub-section “Event parameters in templates” (developer.servicenow.com), lines 5-7.