Security Note: These Settings Require Administrative Access
To access the System Settings views, your 25Live user must be in the System Administrator (-1) security group. If you would like any of the described settings changed for your instance of 25Live, contact your 25Live administrator.
About Template Variables
Event Save Email allows 25Live administrators to set up scenarios outlining the rules under which custom emails will be sent if the user is using the 25Live Pro Event Form. Once you specify all your desired parameters, you can choose or create email templates, including report attachments. One or more emails can be triggered upon event save, either when creating or editing.
Image: Template Variables can be used in the address field of the email.
Image: Template Variables can be used in the subject fields as well as in the body of the email.
Note: Custom Documents Also use Variables
Check out the following article for more information: Document Management Variable Reference and Examples
Template Variables by Dropdown Menu
The variables below are found in the Template Variables dropdown menus.
Template variables can be typed directly from the list below or selected from the expanded Template Variables section within the application. To find a variable, search for a data field in one of the dropdown menus and select its name. Once a variable is selected, you may click on its text to copy it to your clipboard. Paste this text into the body of your template.
Image: Template Variables section of the Create New Template window.
Note: Pre-Save Variables
Most variables are based on an event's details after any changes are saved. But some come in two forms:
- a normal form, such as {{$pro.vars.eventName}}
- a "pre-save" form, such as {{$pro.vars.preEventName}} (indicated by "pre")
These "pre-save" variables will display event details that were in place before any changes were saved to it. These variables can be useful if you want a document to reference previous information.
Take care to distinguish between "pre-save" variables and "preference" variables, which look similar:
- Preference variables include "pref" in the name and include lists of location or resource preferences (such as appear in drafts or requests) instead of actual assignments
Standard Event Variables
Note: Table Output Appearance May Differ
The alignment and appearance output of tables in 25Live Pro looks similar to the example image below.
Image: Example output of $pro.vars.occurrencesWithLocationsString variable.
Title | Variable | Example Output | |||||||||||||||||||||||||||||||||||
Event ID | {{$pro.vars.eventId}} | 188073 Returns the system ID of the event, as seen in the event URL. | |||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Event Link | {{$pro.vars.eventLink}} | <a href="https://25live.collegenet.com/pro/testinstance#!/home/event/21659/details "target="_blank">Event Details</a> Note: Do not use the event link in the Subject field, which does not support HTML tags. | |||||||||||||||||||||||||||||||||||
Event URL | {{$pro.vars.eventUrl}} | https://25live.collegenet.com/pro/testinstance#!/home/event/21659/details | |||||||||||||||||||||||||||||||||||
Event Reference | {{$pro.vars.eventLocator}} | 2023-AAZHLW | |||||||||||||||||||||||||||||||||||
Event Name | {{$pro.vars.eventName}} {{$pro.vars.preEventName}} | Test Event | |||||||||||||||||||||||||||||||||||
Event Title | {{$pro.vars.eventTitle}} {{$pro.vars.preEventTitle}} | Test Title | |||||||||||||||||||||||||||||||||||
Version Number | {{$pro.vars.versionNumber}} {{$pro.vars.preVersionNumber}} | Possible values:
| |||||||||||||||||||||||||||||||||||
Event Type ID | {{$pro.vars.eventTypeId}} {{$pro.vars.preEventTypeId}} | 51 | |||||||||||||||||||||||||||||||||||
Event Type Name | {{$pro.vars.eventTypeName}} {{$pro.vars.preEventTypeName}} | Meeting | |||||||||||||||||||||||||||||||||||
Event Description | {{$pro.vars.description}} | Test Description | |||||||||||||||||||||||||||||||||||
Internal Notes | {{$pro.vars.internalNote}} | Internal notes | |||||||||||||||||||||||||||||||||||
Confirmation Notes | {{$pro.vars.confirmationNote}} | Confirmation notes | |||||||||||||||||||||||||||||||||||
Comments | {{$pro.vars.comment}} | Comment text | |||||||||||||||||||||||||||||||||||
Expected Head Count | {{$pro.vars.expectedCount}} {{$pro.vars.preExpectedCount}} | 12 | |||||||||||||||||||||||||||||||||||
Registered Head Count | {{$pro.vars.registeredCount}} {{$pro.vars.preRegisteredCount}} | 10 | |||||||||||||||||||||||||||||||||||
Event State ID | {{$pro.vars.state}} {{$pro.vars.preState}} | Possible values:
| |||||||||||||||||||||||||||||||||||
Event State Name | {{$pro.vars.stateName}} {{$pro.vars.preStateName}} | Tentative | |||||||||||||||||||||||||||||||||||
Requestor Email | {{$pro.vars.requesterEmail}} {{$pro.vars.requestorEmail}} {{$pro.vars.preRequesterEmail}} | smith.john@school.edu Note: Both spellings of the variable are allowed. | |||||||||||||||||||||||||||||||||||
Scheduler Email | {{$pro.vars.schedulerEmail}} {{$pro.vars.preSchedulerEmail}} | smith.jane@school.edu | |||||||||||||||||||||||||||||||||||
Current Contact Name | {{$pro.vars.currentContactName}} {{$pro.vars.preCurrentContactName}} | Jane Smith | |||||||||||||||||||||||||||||||||||
Primary Org ID | {{$pro.vars.primaryOrganization.itemId}} {{$pro.vars.prePrimaryOrganization.itemId}} | 71 | |||||||||||||||||||||||||||||||||||
Primary Org Name | {{$pro.vars.primaryOrganization.itemName}} {{$pro.vars.prePrimaryOrganization.itemName}} | ATHLETICS | |||||||||||||||||||||||||||||||||||
Primary Org Title | {{$pro.vars.primaryOrganization.itemTitle}} {{$pro.vars.prePrimaryOrganization.itemTitle}} | Athletics Department | |||||||||||||||||||||||||||||||||||
Primary Org Type | {{$pro.vars.primaryOrganization.type}} {{$pro.vars.prePrimaryOrganization.type}} |
| |||||||||||||||||||||||||||||||||||
Primary Org Rating | {{$pro.vars.primaryOrganization.rating}} {{$pro.vars.prePrimaryOrganization.rating}} | Good | |||||||||||||||||||||||||||||||||||
Primary Org Account Number | {{$pro.vars.primaryOrganization.accountNumber}} {{$pro.vars.prePrimaryOrganization.accountNumber}} | 735 | |||||||||||||||||||||||||||||||||||
Event Creation Date | {{$pro.vars.dates.creationDateString}} {{$pro.vars.preDates.creationDateString}} | Wed Jan 27 2024 | |||||||||||||||||||||||||||||||||||
Event Creation Date and Time | {{$pro.vars.dates.creationDateTimeString}} {{$pro.vars.preDates.creationDateTimeString}} | Wed Jan 27 2024 3:10 pm | |||||||||||||||||||||||||||||||||||
Event Creation Time | {{$pro.vars.dates.creationTimeString}} {{$pro.vars.preDates.creationTimeString}} | 3:10 pm | |||||||||||||||||||||||||||||||||||
Current Local Date | {{$pro.vars.dates.currentLocalDateString}} {{$pro.vars.preDates.currentLocalDateString}} | Wed Jan 27 2024 | |||||||||||||||||||||||||||||||||||
Current Local Date and Time | {{$pro.vars.dates.currentLocalDateTimeString}} {{$pro.vars.preDates.currentLocalDateTimeString}} | Wed Jan 27 2024 3:10 pm | |||||||||||||||||||||||||||||||||||
Current Local Time | {{$pro.vars.dates.currentLocalTimeString}} {{$pro.vars.preDates.currentLocalTimeString}} | 3:10 pm | |||||||||||||||||||||||||||||||||||
Last Edit Date | {{$pro.vars.dates.lastModDateString}} {{$pro.vars.preDates.lastModDateString}} | Wed Jan 27 2024 | |||||||||||||||||||||||||||||||||||
Last Edit Date and Time | {{$pro.vars.dates.lastModDateTimeString}} {{$pro.vars.preDates.lastModDateTimeString}} | Wed Jan 27 2024 3:10 pm | |||||||||||||||||||||||||||||||||||
Last Edit Time | {{$pro.vars.dates.lastModTimeString}} {{$pro.vars.preDates.lastModTimeString}} | 3:10 pm | |||||||||||||||||||||||||||||||||||
Setup Date | {{$pro.vars.dates.eventSetupDateString}} {{$pro.vars.preDates.eventSetupDateString}} | Wed Jan 27 2024 | |||||||||||||||||||||||||||||||||||
Setup Date and Time | {{$pro.vars.dates.eventSetupDateTimeString}} {{$pro.vars.preDates.eventSetupDateTimeString}} | Wed Jan 27 2024 3:10 pm | |||||||||||||||||||||||||||||||||||
Setup Time | {{$pro.vars.dates.eventSetupTimeString}} {{$pro.vars.preDates.eventSetupTimeString}} | 3:10 pm | |||||||||||||||||||||||||||||||||||
Pre-Event Date and Time | {{$pro.vars.dates.preEventDateTimeString}} {{$pro.vars.preDates.preEventDateTimeString}} | Wed Jan 27 2024 3:10 pm | |||||||||||||||||||||||||||||||||||
Pre-Event Time | {{$pro.vars.dates.preEventTimeString}} {{$pro.vars.preDates.preEventTimeString}} | 3:10 pm | |||||||||||||||||||||||||||||||||||
Start Date | {{$pro.vars.dates.eventStartDateString}} {{$pro.vars.preDates.eventStartDateString}} | Wed Jan 27 2024 | |||||||||||||||||||||||||||||||||||
Start Date and Time | {{$pro.vars.dates.eventStartDateTimeString}} {{$pro.vars.preDates.eventStartDateTimeString}} | Wed Jan 27 2024 3:10 pm | |||||||||||||||||||||||||||||||||||
Start Time | {{$pro.vars.dates.eventStartTimeString}} {{$pro.vars.preDates.eventStartTimeString}} | 3:10 pm | |||||||||||||||||||||||||||||||||||
End Date | {{$pro.vars.dates.eventEndDateString}} {{$pro.vars.preDates.eventEndDateString}} | 3:10 pm | |||||||||||||||||||||||||||||||||||
End Date and Time | {{$pro.vars.dates.eventEndDateTimeString}} {{$pro.vars.preDates.eventEndDateTimeString}} | Wed Jan 27 2024 3:10 pm | |||||||||||||||||||||||||||||||||||
End Time | {{$pro.vars.dates.eventEndTimeString}} {{$pro.vars.preDates.eventEndTimeString}} | 3:10 pm | |||||||||||||||||||||||||||||||||||
Post-Event Date | {{$pro.vars.dates.postEventDateString}} {{$pro.vars.preDates.postEventDateString}} | Wed Jan 27 2024 | |||||||||||||||||||||||||||||||||||
Post-Event Date and Time | {{$pro.vars.dates.postEventDateTimeString}} {{$pro.vars.preDates.postEventDateTimeString}} | Wed Jan 27 2024 3:10 pm | |||||||||||||||||||||||||||||||||||
Post-Event Time | {{$pro.vars.dates.postEventTimeString}} {{$pro.vars.preDates.postEventTimeString}} | 3:10 pm | |||||||||||||||||||||||||||||||||||
Takedown Date | {{$pro.vars.dates.eventTakedownDateString}} {{$pro.vars.preDates.eventTakedownDateString}} | Wed Jan 27 2024 | |||||||||||||||||||||||||||||||||||
Takedown Date and Time | {{$pro.vars.dates.eventTakedownDateTimeString}} {{$pro.vars.preDates.eventTakedownDateTimeString}} | Wed Jan 27 2024 3:10 pm | |||||||||||||||||||||||||||||||||||
Takedown Time | {{$pro.vars.dates.eventTakedownTimeString}} {{$pro.vars.preDates.eventTakedownTimeString}} | 3:10 pm | |||||||||||||||||||||||||||||||||||
Setup Duration | {{$pro.vars.durations.setup}} {{$pro.vars.preDurations.setup}} | 1 Hour, 30 Minutes | |||||||||||||||||||||||||||||||||||
Pre-Event Duration | {{$pro.vars.durations.preEvent}} {{$pro.vars.preDurations.preEvent}} | 1 Hour, 30 Minutes | |||||||||||||||||||||||||||||||||||
Event Duration | {{$pro.vars.durations.event}} {{$pro.vars.preDurations.event}} | 1 Hour, 30 Minutes | |||||||||||||||||||||||||||||||||||
Post-Event Duration | {{$pro.vars.durations.postEvent}} {{$pro.vars.preDurations.postEvent}} | 1 Hour, 30 Minutes | |||||||||||||||||||||||||||||||||||
Takedown Duration | {{$pro.vars.durations.takedown}} {{$pro.vars.preDurations.takedown}} | 1 Hour, 30 Minutes | |||||||||||||||||||||||||||||||||||
Pre-Event to Post-Event Duration | {{$pro.vars.durations.preToPost}} {{$pro.vars.preDurations.preToPost}} | 1 Hour, 30 Minutes | |||||||||||||||||||||||||||||||||||
Setup to Takedown Duration | {{$pro.vars.durations.setupToTakedown}} {{$pro.vars.preDurations.setupToTakedown}} | 1 Hour, 30 Minutes | |||||||||||||||||||||||||||||||||||
Occurrence Table | {{$pro.vars.occurrencesString}} {{$pro.vars.preOccurrencesString}} |
| |||||||||||||||||||||||||||||||||||
Occurrence List | {{$pro.vars.occurrencesStringCSV}} {{$pro.vars.preOccurrencesStringCSV}} | ||||||||||||||||||||||||||||||||||||
Occurrence and Location Table | {{$pro.vars.occurrencesWithLocationsString}} {{$pro.vars.preOccurrencesWithLocationsString}} |
| |||||||||||||||||||||||||||||||||||
Occurrence and Resource Table | {{$pro.vars.occurrencesWithResourcesString}} {{$pro.vars.preOccurrencesWithResourcesString}} |
| |||||||||||||||||||||||||||||||||||
Occurrence Location Resource Table | {{$pro.vars.occurrencesWithLocationsAndResourcesString}} {{$pro.vars.preOccurrencesWithLocationsAndResourcesString}} |
| |||||||||||||||||||||||||||||||||||
Location Table | {{$pro.vars.locationsString}} {{$pro.vars.preLocationsString}} |
| |||||||||||||||||||||||||||||||||||
Location List | {{$pro.vars.locationsStringCSV}} {{$pro.vars.preLocationsStringCSV}} | ||||||||||||||||||||||||||||||||||||
Resource Table | {{$pro.vars.resourcesString}} {{$pro.vars.preResourcesString}} |
| |||||||||||||||||||||||||||||||||||
Resource List | {{$pro.vars.resourcesStringCSV}} {{$pro.vars.preResourcesStringCSV}} | ||||||||||||||||||||||||||||||||||||
Pref Occurrence and Location Table | {{$pro.vars.prefOccurrencesWithLocationsString}} {{$pro.vars.prePrefOccurrencesWithLocationsString}} |
| |||||||||||||||||||||||||||||||||||
Pref Occurrence and Resource Table | {{$pro.vars.prefOccurrencesWithResourcesString}} {{$pro.vars.prePrefOccurrencesWithResourcesString}} |
| |||||||||||||||||||||||||||||||||||
Pref Occurrence Location Resource Table | {{$pro.vars.prefOccurrencesWithLocationsAndResourcesString}} {{$pro.vars.prePrefOccurrencesWithLocationsAndResourcesString}} |
| |||||||||||||||||||||||||||||||||||
Pref Location Table | {{$pro.vars.prefLocationsString}} {{$pro.vars.prePrefLocationsString}} |
| |||||||||||||||||||||||||||||||||||
Pref Location List | {{$pro.vars.prefLocationsStringCSV}} {{$pro.vars.prePrefLocationsStringCSV}} | ARTS 101, ARTS 103, ARTS 105 | |||||||||||||||||||||||||||||||||||
Pref Resource Table | {{$pro.vars.prefResourcesString}} {{$pro.vars.prePrefResourcesString}} |
| |||||||||||||||||||||||||||||||||||
Pref Resource List | {{$pro.vars.prefResourcesStringCSV}} {{$pro.vars.prePrefResourcesStringCSV}} | AV - MAC, AV - Projector, AV - PC | |||||||||||||||||||||||||||||||||||
Current Group ID | {{$pro.vars.currentGroupId}} | -1 Returns the security group ID of the user editing the event. | |||||||||||||||||||||||||||||||||||
Home URL | {{$pro.vars.homeUrl}} | The URL of your 25Live instance. |
Current Template Name | {{$pro.vars.template}} {{$pro.vars.preTemplate}} | |
Triggering Scenario Name | {{$pro.vars.scenario}} {{$pro.vars.preScenario}} |
Note: Using Code View?
Curly brackets { } aren't needed in Code View. When generating Code Variable, brackets will be omitted.
Image: Event Save Email Code Variables.
Event Roles
Before you can select an Event Role contact variable, you'll need to choose a value from the Event Roles dropdown.
Then, select the variable format for the contact role.
Tip: Most Common Contact Roles
These are the IDs of the most common contact roles in 25Live:
Event Requestor:
-1
Event Scheduler:
-2
Contact Role Variables
To use the event role variables, replace the italicized text with the system ID for the contact role. If you need the IDs, see Finding Object IDs in 25Live for more information.
Title | Variable | Example Output |
---|---|---|
Contact ID | {{$pro.vars.roleContactId.-2}} | 542 |
Full Name | {{$pro.vars.roleContactName.ID}} {{$pro.vars.preRoleContactName.ID}} | Mozart, Wolfgang A. |
First Name | {{$pro.vars.roleContactFirst.ID}} {{$pro.vars.preRoleContactFirst.ID}} | Wolfgang |
Last Name | {{$pro.vars.roleContactLast.ID}} {{$pro.vars.preRoleContactLast.ID}} | Mozart |
Middle Name | {{$pro.vars.roleContactMiddle.ID}} {{$pro.vars.preRoleContactMiddle.ID}} | Amadeus |
{{$pro.vars.roleContactEmail.ID}} | name@school.edu | |
Address | {{$pro.vars.roleContactAddr.ID}} {{$pro.vars.preRoleContactAddr.ID}} | 123 Work St. Portland OR 97205 |
Phone | {{$pro.vars.roleContactPhone.ID}} {{$pro.vars.preRoleContactPhone.ID}} | (503) 555-0091 |
Fax | {{$pro.vars.roleContactFax.ID}} {{$pro.vars.preRoleContactFax.ID}} | (503) 555-0091 |
Custom Attributes
To use the custom attribute variables, replace the italicized text with the system ID for the custom attribute. If you need the IDs, see Finding Object IDs in 25Live for more information.
Title | Variable | Example Use |
---|---|---|
(Choose from your available custom attributes) | {{$pro.vars.customAttributes.ID}} {{$pro.vars.preCustomAttributes.ID}} | {{$pro.vars.customAttributes.23}} |
Formattable Date Variables
While some of these variables are found in the Standard Event Variables menu, the most accurate and convenient way to retrieve date/time variables is to open the Formattable Date Variables section to generate the exact variables you need that match the example shown.
Each of these date variables offers a Format choice to choose one of many standard date/time formats from a dropdown menu. The examples below show the variable with the shorthand date and time (M/d/yy, h:mm a)
To manually format a date variable, choose one of the date values below and add the desired date code after a pipe bar | character.
Example: {{$pro.vars.dates.eventstartDate | short}}
Title | Modification | Variable (with a format option chosen) |
---|---|---|
Creation Date | Choose Format | {{$pro.vars.dates.creationDate | short}} |
Current Local Date | Choose Format | {{$pro.vars.dates.currentLocalDate | short}} |
Last Edit Date | Choose Format | {{$pro.vars.dates.lastModDate | short}} |
Setup Date | Choose Format | {{$pro.vars.dates.eventSetupDate | short}} |
Pre-Event Date | Choose Format | {{$pro.vars.dates.preEventDate | short}} |
Event Start Date | Choose Format | {{$pro.vars.dates.eventStartDate | short}} |
Event End Date | Choose Format | {{$pro.vars.dates.eventEndDate | short}} |
Post Event Date | Choose Format | {{$pro.vars.dates.postEventDate | short}} |
Takedown Date | Choose Format | {{$pro.vars.dates.eventTakedownDate | short}} |
Date and Time Format Options
Title | Variable Text | Example Output |
M/d/yy, h:mm a | short | 6/15/23, 9:03 AM |
---|---|---|
MMM d, y, h:mm:ss a | medium | Jun 15, 2023, 9:03:01 AM |
MMMM d, y, h:mm:ss a z | long | June 15, 2023 at 9:03:01 AM GMT+1 |
EEEE, MMMM d, y, h:mm:ss a zzzz | full | Monday, June 15, 2023 at 9:03:01 AM GMT+01:00 |
M/d/yy | shortDate | 6/15/23 |
MMM d, y | mediumDate | Jun 15, 2023 |
MMMM d, y | longDate | June 15, 2023 |
EEEE, MMMM d, y | fullDate | Monday, June 15, 2023 |
h:mm a | shortTime | 9:03 AM |
h:mm:ss a | mediumTime | 9:03:01 AM |
h:mm:ss a z | longTime | 9:03:01 AM GMT+1 |
h:mm:ss a zzzz | fullTime | 9:03:01 AM GMT+01:00 |
Table Builder
The Table Builder and dropdown allows you to organize data more data easily, without having to create tables manually. To create a table, make a table selection from the Table Builder dropdown menu.
Table Options:
|
The table selection will populate data that will represent columns once your table is generated. Each column will have a Column Name, a Variable, and occasionally a Format option.
The number of columns generated by default will depend on the number of available variables for the table type selected. For example, the Related Events table (pictured below) has five variable options (ID, Event Name, Event Title, Start Date, & End Date) so a column is populated for each of them.
- Select your Column Name, Variable, and Format values
- Each Column Name populates with a default label that matches the associated variable; these labels can be edited.
- The variables available in the Variable dropdowns are specific to the table type selected.
- When a formattable date variable is selected, use the Format dropdown to choose the date and time structure of that variable.
- The table builder also features a Width of the column relative to other columns. All of these values are added together and the relative width of any individual column is its value divided by the sum.
- Add Columns or Delete columns as needed.
- Once you've made your selections, copy and paste the variable output into your template/document.
Examples (Click to Expand)
Example Table Configurations:
Example Table Preview:
List Builder
The List Builder and dropdown allows you to organize data more data easily, without having to create lists manually. To create a table, make a table selection from the List Builder dropdown menu.
![]() | List Options:
|
- Next, choose a Variable from the dropdown. These options will depend on your List Builder selection.
- Copy and paste the variable into your template/document.
Examples (Click to Expand)
Example List Configurations:
Example List Preview:
Other Useful Variables
These variables are not found in dropdown menus but may still be useful in your template.
Organization and Contact Details
These variables return details about organizations attached to an event as well as contacts (such as Billing Contacts) for those organizations.
To use them, replace the red, italicized text with the system ID of an organization and/or an organization contact role. You can locate these in System Settings → Master Definitions. See Finding Object IDs in 25Live for more information.
Example:
{{$pro.vars.organizations.98.contacts.-1.role}} 98 is the orgID for the organization -1 is the roleID for the contact role |
Tip: Common Organization and Contact IDs
These are the two most common IDs you'll want to use:
- For an event's primary organization, use the designated "primaryOrganization" variable instead of looking up its ID
- The system-defined Billing Contact roleID is -1
Value | Variable | Example Output |
---|---|---|
Organization Name | {{$pro.vars.organizations.orgID.itemName}} | ATHLETICS |
Organization Title | {{$pro.vars.organizations.orgID.itemTitle}} | Athletics Department |
Contact Role | {{$pro.vars.organizations.orgID.contacts.roleID.role}} {{$pro.vars.primaryOrganization.contacts.roleID.role}} | Billing Contact |
Contact Name | {{$pro.vars.organizations.orgID.contacts.roleID.itemName}} {{$pro.vars.primaryOrganization.contacts.roleID.itemName}} | Smith, John |
Contact Title | {{$pro.vars.organizations.orgID.contacts.roleID.itemTitle}} {{$pro.vars.primaryOrganization.contacts.roleID.itemTitle}} | Treasurer |
Contact Email | {{$pro.vars.organizations.orgID.contacts.roleID.email}} {{$pro.vars.primaryOrganization.contacts.roleID.email}} | smith.john@school.edu |
Contact Phone | {{$pro.vars.organizations.orgID.contacts.roleID.phone}} {{$pro.vars.primaryOrganization.contacts.roleID.phone}} | (503) 290-0091 |
Contact Fax | {{$pro.vars.organizations.orgID.contacts.roleID.fax}} {{$pro.vars.primaryOrganization.contacts.roleID.fax}} | (503) 290-0091 |
Contact Address | {{$pro.vars.organizations.orgID.contacts.roleID.address}} {{$pro.vars.primaryOrganization.contacts.roleID.address}} | 805 SW Broadway Portland, OR 97205 |
Pricing
The following variables give the total pricing for a single event or a group of related events.
Value | Variable | Example Output | Notes |
---|---|---|---|
Grand Total | {{$pro.vars.pricing.grandTotal}} | 96.4 | Pricing total for a single event, formatted as a number |
Grand Total (currency) | {{$$pro.vars.pricing.grandTotal}} | $96.40 | Pricing total for a single event, formatted as currency |
Email Recipient Shortcuts
These special recipient shortcuts are available for use in the To, CC, and BCC fields.
Shortcut | Recipient |
---|---|
object owner | The event's owner |
service providers | Any user with approval workflow (notifications) |
assigners | Any user with assignment policy workflow |
attendees | Users of all registration statuses |
attendees1 | Users with registration status: Expressed Interest |
attendees2 | Users with registration status: Unconfirmed |
attendees3 | Users with registration status: Wait List |
attendees4 | Users with registration status: Confirmed |
attendees5 | Users with registration status: No Show |
attendees6 | Users with registration status: Cancelled |
Special Functions and Formatting
Adding Conditional Logic
Conditional logic allows you to determine what is displayed—based on whether certain conditions are met—using the format:{{( expression )}}
Examples:
- In this example, "Created" displays if the event version number is 0 (indicating that it is a new event). Otherwise, "Edited" displays.
{{( {{$pro.vars.versionNumber}} === 0 ? "Created" : "Edited" )}}
(See animation below) - Conditional logic also works with variables. Similar to the example above, here, the Event Name or Event Title displays depending on if the event is new or edited.
{{( {{$pro.vars.versionNumber}} === 0 ? "{{$pro.vars.eventName}}" : "{{$pro.vars.eventTitle}}" )}}
Please note that this condition allows for word wrap, but not line breaks. Each paragraph will need its own conditional statement. (See animation below)- Additional example:
{{( "{{$pro.vars.customAttributes.Number}}" === "Yes" ? "Attribute is true" : "Attribute is false" )}}
— note the different placement of quotes for different situations
- Additional example:
Animation: Adding conditional logic using the examples above.
Date Modification
You can modify any variable with "Date" or "Time" in its name (including formattable date variables) by adding/subtracting days, hours, or minutes. Replace X in the following values with the number you wish to add or subtract:
- Xd (days)
- Xh (hours)
- Xm (minutes)
You can change a variable with multiple values at once by putting them together one after another.
Date Modification | Effect |
---|---|
{{$pro.vars.dates.creationDateTimeString}} | Basic date |
{{$pro.vars.dates.creationDateTimeString + 5d}} | Five days later |
{{$pro.vars.dates.creationDateTimeString + 5d - 3h}} | Five days later and three hours earlier |
{{$pro.vars.dates.creationDate + 5d | short}} | Five days later with a "short" date format |
Basic Math
Any variable which returns a number can have basic arithmetic operations applied to it:
- addition: +
- subtraction: -
- multiplication: *
- division: /
Add these operations within the curly brackets at the end of the variable. It is useful to combine this with currency formatting for displaying prices and discounts.
Variable | Example Output | Use Case |
---|---|---|
{{$$pro.vars.pricing.grandTotal}} | $96.40 | Base price |
{{$$pro.vars.pricing.grandTotal * .2}} | $19.28 | 80% discount |
{{$$pro.vars.pricing.grandTotal - 50}} | $46.40 | $50 discount |