Event Inputs

Event inputs are used to pass information from a triggered expression to the event, and on to the event's action/alarm.

This section explains how the embed formula is used to embed an event's input values into its description and action's content.

See Embed Node Information to learn how to pass information from a triggered expression to the event inputs.

Input formula must begin with "${" and end with "}".
Content enclosed within the brackets consist of 1 to 2 words, separated by ".".
- General: ${<input_name>.<2nd word>}
- input_name refers to user-defined inputs
- 2nd_word is used to format the embedded value

Fill in the "Inputs" field.
Select the user-defined input you want to embed.
- They are shown in the Click to embed input field (under the message of an event's action/event's description box).

The CMS supports two types of formatting:

Note:Value of <input_name> must be a number.

Note:Value of <input_name> must be a datetime.

Dates are parsed using Moment in UTC mode. Refer to docs here.

You can format dates using:

Organization's default date-time & UTC offset: ${<input_name>.to_date_str()}
- E.g. {date_of_incident.to_date_str()}
Specified <preset> format & organization's default UTC offset: ${<input_name>.to_date_str(<preset>)}
- E.g. ${date_of_incident.to_date_str(iso)}
Specified <preset> format & <utc_offset>: ${<input_name>.to_date_str(<preset> <utc_offset>)}
- E.g. ${date_of_incident.to_date_str(iso -10)} or ${date_of_incident.to_date_str(iso +10)}
Specified <format> & <utc_offset>: ${<input_name>.to_date_str(<format> <utc_offset>)}
- E.g. ${date_of_incident.to_date_str(MM/DD/YYYY -10)} or ${date_of_incident.to_date_str(MM/DD/YYYY HH:mm +10)}

Note:

For <utc_offset> only the first two digits will be considered.
For <format>, "HH" refers to hours in a day (24-hour clock) and "hh" refers to hours in am/pm format (12-hour clock).

V2/CMS Tutorial/User Tools/Creating Content/Automation/Event/Inputs