Global AlertLink supports three types of substitutions that can be utilized in pre-planned broadcast messages: SYSTEM, PROMPT, and FORM. All substitution parameters follow the following syntax: ${PARAMTYPE:FIELDVALUE:DEFAULTVALUE}.
Global AlertLink supports substitutions that can be utilized in pre-planned broadcast messages:
System Parameters
A SYSTEM parameter type will be evaluated and replaced at the plan / event activation time. The user may add a SYSTEM parameter type within the Short Text or Full Text of a pre-planned message.
The following field values are valid for the SYSTEM parameter type:
Field Value | Description |
${SYSTEM:EVENTDATE} | Event activation date |
${SYSTEM:EVENTFULLDATE} | Event activation date in long date format |
${SYSTEM:EVENTTIME} | Event activation date in long date format |
${SYSTEM:EVENTOWNER} | Owner of Event |
${SYSTEM:ACTIVATEDBY} | User that Activated the Event |
${SYSTEM:EVENTTITLE} | Event Title |
${SYSTEM:EVENTSEVERITY} | Event Severity |
${SYSTEM:EVENTINTERRUPTION} | Event Interruption Level |
${SYSTEM:EVENTORGANIZATION} | Organization of the Event |
${SYSTEM:EVENTLINK} | URL for the Event |
Prompt Parameters
A PROMPT parameter will be replaced by data collected from the activating user. When a plan is activated, the user who activates the plan will be presented with an additional form listing all the PROMPT parameter types. This form will only appear when a broadcast message contains a message substitution. The user will be able to supply values for each of these parameters at this time. The parameters in the messages will be replaced with the values collected in this step.
Form Parameters
All FORM parameter will be evaluated using one of two methods. The first method will collect values from the Incident Submission Form used to activate the event, and use those values to replace the matching message parameters. If the plan is activated from the main Global AlertLink interface, or the incident submission form does not contain the field value, each FORM parameters will then behave like a PROMPT parameter for the event activation.
Once the plan has been activated, the user who activates the plan will be presented with an additional form listing all the PROMPT parameter types. This form will only appear when a broadcast message contains a message substitution. The user will be able to supply values for each of these parameters at this time. The parameters in the messages will be replaced with the values collected in this step.
Once the plan has been activated and the message has been sent, the broadcast message will now become part of the event. Now the parameters can be viewed as they were sent to recipients via the message.
Below is an example using message substitution.
${SYSTEM: ACTIVATEDBY} has just reported a fire at the ${FORM:Location} facility. All response team personnel should stand by for further details. ${PROMPT:Coordinator:John Doe} will act as coordinator for the event.
Message substitution can be placed in the Subject of a message.
