Variables

Variables are available throughout the system to develop dynamic lists of data sets, use specific dates and times as input values, and call on data from modules throughout the system to be used in other modules. Variables are denoted by a set of curly brackets: {Variable}.

Where variables are allowed, view the entire list of variables by entering “{“ into the text field. From there, continue typing the variable name and inputs, or select a variable from the dropdown list. Not every variable displayed in the dropdown list will be applicable to the text field being edited.

Alternate Name

• • Format: {Asset.AlternateName: Asset ID or External ID}
  • Description: The alternate name of a specific asset. Insert the asset’s external identifier or 36-character GUID.
  • Examples:
    • {Asset.AlternateName:Engine_01}
    • {Asset.AlternateName: d445e351-e93b-4e35-89f6-8a9b23cc8495}
  • Applications: Form Type, Task Type

As of Date

• • Format: {AsOfDate}
  • Description: Prompts the user for a single date and filters for all dates greater than or equal to this date.
    • A report with this variable set to the “first day of this year” will automatically roll over to the next year on January 1.
  • Example: Telemetry.ActiveDate >= {AsOfDate}
  • Applications: Report

Asset

• • Format: {Asset:Asset ID or External ID} 
  • Description: A specific asset. Insert the asset’s external identifier or 36-character GUID.
    • When multiple assets are permitted (such as when a workflow generates a task for multiple assets), separate each variable with a colon (;). For example: {Asset:Asset ID1};{Asset:Asset ID2}
  • Examples:
    • {Asset:Engine_01}
    • {Asset: d445e351-e93b-4e35-89f6-8a9b23cc8495}
  • Applications: Form Type, Report, Workflow

Asset (Report dropdown filter)

• • Format: {AssetID}
  • Description: An asset in the system. No inputs to the variable are necessary.
    • To configure a report filter to select a value from a list of assets, you will need to set the Value field to an ID rather than a name. For example: Asset.Asset ID = {AssetID} will allow you to filter by a single asset chosen from the list of all assets.
  • Example: Asset.Asset ID = {AssetID}
  • Applications: Report

Asset Address

• • Format: {AssetAddress:Asset ID or External ID,Address Type,Address Property}
  • Description: A portion of an asset’s address.
    • If more than one address of the same type is marked as “Use”, the first match will be returned.
    • Input the Asset’s external identifier or 36-character GUID, the Address Type (name or external identifier), and the Address Property.
    • Please specify one of the following Address Properties: Street1, Street2, City, State.Name, State.Code, PostalCode, Country.Name, Country.Code, County.Name, County.Code.
    • If the Address Property is blank, or any unsupported property is entered, the variable will return the full address on a single line.
  • Examples:
    • {AssetAddress:{FormAnswer:Facility},Physical,Street1}
    • {AssetAddress: 3d367a48-8b09-46c7-bd08-95d2763802a2,Mailing,State.Code}
  • Applications: Form Type

Asset Attribute (Form)

• • Format: {AssetAttribute:Asset ID or External ID,Attribute Type ID or External ID}
  • Description: A value from an asset attribute. Insert the Asset’s and Attribute Type’s external identifiers or 36-character GUIDs. The Attribute Type must be defined at the asset’s Asset Type. Answers to form questions may be nested inside of this variable (please see the examples below).
  • Examples:
    • {AssetAttribute: Engine_CE01, FuelType}
    • (AssetAttribute:{FormAnswer:EngineName}, FuelType}
  • Applications: Form Type

Asset Attribute (Reports, Task Types, and Workflows)

• • Format: {AssetAttribute:Attribute Type ID or External ID,Asset Type}
  • Description: A value from an asset attribute. Insert the Attribute Type’s external identifier or 36-character GUID.
    • This variable will only work in table reports where Asset is selected as the Datasource. To use this in a table report, for each column that will have an asset attribute, you must select Advanced Features.Calculated Field as the Column field and choose the {AssetAttribute:Attribute Type ID or External ID} variable in the Calculated Field. Use of the Alias field is highly recommended for identifying the attribute in each column. Please see Calculated Fields for more information.
    • For Asset Attributes that span multiple record types, please specify the record type within the variable (as in the last example).
  • Examples:
    • {AssetAttribute:Condition}
    • {AssetAttribute: a9fe3517-da98-46ff-b990-6f0e5687458e}
    • {AssetAttribute:StartDate, Engine}
  • Applications: Report, Task Type, Workflow

Asset Contact(s)

• • Format: {AssetContacts:Asset ID or External ID,Contact Role ID or External ID}
  • Description: The contacts associated with the asset identified and with the contact role identified. Insert the asset external identifier or 36-character GUID and the contact role external identifier or 36-character GUID.
    • If more than one contact is returned, if written to a dropdown form answer, the first contact (alphabetically) will be chosen. If written to a text field, all contacts will be returned, separated by commas.
  • Example: {AssetContacts:{FormAnswer:Facility},Manager}
  • Applications: Form Type

Asset In-Service Date

• • Format: {Asset.InServiceDate:<Asset ID or External ID>}
  • Description: Inserts the In-Service Date of the asset. If the asset is not found, or a date does not exist, nothing is inserted. Use the asset external identifier or 36-character GUID.
  • Example: {Asset.InServiceDate:{TriggeringAssetID}}
  • Applications: Report, Work, Workflow

Asset Photo

• • Format: {Asset.Photo:}
  • Description:

    Inserts a photo of the asset in the email body that’s triggered by a workflow. If the asset is not found, or a representative photo does not exist, nothing is inserted in the email. Insert the asset external identifier or 36-character GUID. This variable currently works in email notifications only, not SMS notifications.

  • Example: {Asset.Photo:{TriggeringAssetID}}
  • Applications: Workflow

Asset Retired Date

• • Format: {Asset.RetiredDate:<Asset ID or External ID>}
  • Description: Inserts the Retired Date of the asset. If the asset is not found, or a date does not exist, nothing is inserted. Use the asset external identifier or 36-character GUID.
  • Example: {Asset.RetiredDate:{TriggeringAssetID}}
  • Applications: Report, Work, Workflow

Asset Type

• • Format: {AssetType:}
  • Description: The type of asset. Insert the asset type external identifier, 36-character GUID, or asset type name.
  • Example: {AssetType:Assetas_Engine}
  • Applications: Form Type, Task Type, Workflow

Associated Contact(s)

• • Format: {AssociatedContacts}
  • Description: Contacts associated with the record(s). There are no inputs to the variable.
    • In Form Type Rules, it returns the contacts associated with the form.
    • In Reports, it returns the contacts associated with the asset(s) that are identified in the report.
    • In Task Type Rules, it returns the contacts associated with the task.
    • In Workflows, it returns the contacts associated with the asset(s) that triggered the workflow.
  • Example: {AssociatedContacts}
  • Applications: Form Type, Report, Task Type, Workflow

Associated Contact(s) with Role

• • Format: {AssociatedContacts:Contact Role ID or External ID,format}
  • Description: The contacts with a specific role associated with the asset(s) that are identified in the report or that triggered the workflow. Insert the Contact Role’s external identifier or 36-character GUID.
    • This variable will only work in table reports where Asset is selected as the Datasource. To use this in a table report, for each column that will list contacts with a specific role, you must select Advanced Features.Calculated Field as the Column field and choose the {AssociatedContacts:Contact Role ID or External ID} variable in the Calculated Field. Use of the Alias field is highly recommended for identifying the role in each column. Multiple contacts with the same role will be listed and separated with a semicolon. Please see Calculated Fields for more information.
    • This variable accepts the following inputs to format the display name:
      • F – First
      • M – Middle
      • L – Last
      • FL – First Last
      • FML – First Middle Last
      • LF – Last, First
      • LFM – Last, First Middle
  • Examples:
    • {AssociatedContacts:EngineMechanic}
    • {AssociatedContacts:a8bebe1e-68cf-4451-bfc6-7ec05db3157c}
  • Applications: Report, Workflow

Associated Contact(s) with Asset and Role

• • Format: {AssociatedContacts:<Asset ID or External ID>} or {AssociatedContacts:<Asset ID or External ID>, <Format>} or {AssociatedContacts:<Asset ID or External ID>, <Contact Role ID or External ID>} or {AssociatedContacts:<Asset ID or External ID>, <Contact Role ID or External ID>, <Format>}
  • Description: The contacts with an optional specific role associated with the specified asset. Insert the Asset’s external identifier, 36-character GUID, or the {AssociatedAssets} variable and the optional Contact Role’s external identifier or 36-character GUID.
    • This variable accepts the following inputs to format the display name:
      • F – First
      • M – Middle
      • L – Last
      • FL – First Last
      • FML – First Middle Last
      • LF – Last, First
      • LFM – Last, First Middle
  • Examples:
    • {AssociatedContacts:{AssociatedAssets},ProductionCoordinator}
  • Applications: Form Type, Workflow

Associated Contact(s) to Other Contacts or in a Group

• • Format:
    • {AssociatedContacts:Primary Contact ID or External ID,format}
    • {AssociatedContacts:Group ID or External ID,format}
  • Description: The contacts associated to the Primary Contact or within a Group. Insert the Primary Contact’s or Group’s external identifier or 36-character GUID.
    • Contacts are associated by directional associations such that the Primary Contact is the first name in the association and the Secondary Contact is the second name in the same association.  For the following example, “Group A contains John Doe”, Group A is the Primary Contact, while John Doe is the Secondary Contact.
    • Multiple contacts will be returned separated with a semicolon.
    • This variable accepts the following inputs to format the display name:
      • F – First
      • M – Middle
      • L – Last
      • FL – First Last
      • FML – First Middle Last
      • LF – Last, First
      • LFM – Last, First Middle
    • Please note that managed contacts are not the same as associated contacts.
  • Examples:
    • {AssociatedContacts:{FormAnswer:Name},FL}
    • {AssociatedContacts:GroupXYZ,FML}
  • Applications: Form Type, Report, Task Type, Workflow

Blank/Null

• • Format: {Blank}
  • Description: Overwrites a form answer or an asset attribute with a null value. Must be used in conjunction with the ‘Overwrite Values’ toggle. The form answer or asset attribute must be specified in the trigger portion of the rule, but not inputs to the variable are necessary.
  • Example: {Blank}
  • Applications: Form Type, Report, Task Type, Workflow

Calendar Year

• • Format: {CalendarYear}
  • Description: A four-digit calendar year. No inputs to the variable are necessary. When configured in a report or document template filter, this variable will prompt the user to select a calendar year prior to running the report or document template.
  • Example: {CalendarYear}
  • Applications: Document Template, Report

Calendar Year End Date

• • Format: {CalendarYearEndDate}
  • Description: The last day of the calendar year entered (12/31/XXXX). No inputs to the variable are necessary. The {CalendarYearStartDate} and {CalendarYearEndDate} variables may be applied together, but the combination is not required. When configured in a report or document template filter, this variable will prompt the user to select a calendar year prior to running the report or document template.
  • Example: Telemetry.ActiveDate <= {CalendarYearEndDate}
  • Applications: Document Template, Report

Calendar Year Start Date

• • Format: {CalendarYearStartDate}
  • Description: The first day of the calendar year entered (01/01/XXXX). No inputs to the variable are necessary. The {CalendarYearStartDate} and {CalendarYearEndDate} variables may be applied together, but the combination is not required. When configured in a report or document template filter, this variable will prompt the user to select a calendar year prior to running the report or document template.
  • Example: Telemetry.ActiveDate >= {CalendarYearStartDate}
  • Applications: Document Template, Report

Contact

• • Format: {Contact:Contact ID or External ID} or {Contact:Contact ID or External ID,format}
  • Description: A specific contact. Insert the contact’s external identifier or 36-character GUID. This variable accepts the following inputs to format the display name:
    • F – First
    • M – Middle
    • L – Last
    • FL – First Last
    • FML – First Middle Last
    • LF – Last, First
    • LFM – Last, First Middle
  • Examples:
    • {Contact:BillupsJames27210}
    • {Contact: 3d367a48-8b09-46c7-bd08-95d2763802a2}
    • {Contact:SmithBob4589,LFM}
    • {Contact:{FormAnswer:Name},FL}
  • Applications:  Form Type, Report, Task Type, Workflow

Contact (Report dropdown filter)

• • Format: {ContactID}
  • Description: A contact in the system. No inputs to the variable are necessary.
    • To configure a report filter to select a value from a list of contacts, you will need to set the Value field to an ID rather than a name. For example: Contact.Contact ID = {ContactID} will allow you to filter by a single contact chosen from the list of all contacts.
  • Example: Contact.Contact ID = {ContactID}
  • Applications: Report

Contact Address

• • Format: {ContactAddress:Contact ID or External ID,Address Type,Address Property}
  • Description: Inserts a portion of a contact’s address. If more than one address of the same type is marked as “Use”, the first match will be returned.
    • Input the Contact’s external identifier or 36-character GUID, the Address Type (name or external identifier), and the Address Property. Please specify one of the following Address Properties: Street1, Street2, City, State, StateCode, PostalCode, Country, CountryCode, County.
    • If the Address Property is blank, or any unsupported property is entered, the variable will return the full address on a single line.
  • Examples:
    • {ContactAddress:{FormAnswer:Assetas_EmployeeName},Assetas_Home,Street1}
    • {ContactAddress: 3d367a48-8b09-46c7-bd08-95d2763802a2,Mailing,StateCode}
  • Applications: Form Type

Contact Attribute (Form)

• • Format: {ContactAttribute:Contact ID or External ID,Attribute Type ID or External ID}
  • Description: A value from a contact attribute. Insert the Contact’s and Attribute Type’s external identifiers or 36-character GUIDs. The Attribute Type must be defined at the contact’s Contact Type. Answers to form questions may be nested inside of this variable (please see the example).
  • Examples:
    • {ContactAttribute: BillupsJames27210, Title}
    • {ContactAttribute:{FormAnswer:EmployeeName}, Title}
  • Applications: Form Type

Contact Attribute (Reports and Workflow)

• • Format: {ContactAttribute:Attribute Type ID or External ID,Type}
  • Description: A value from a contact attribute. Insert the Attribute Type’s external identifier or 36-character GUID.
    • This variable will only work in table reports where Contact is selected as the Datasource. To use this in a table report, for each column that will have a contact attribute, you must select Advanced Features.Calculated Field as the Column field and choose the {ContactAttribute:Attribute Type ID or External ID} variable in the Calculated Field. Use of the Alias field is highly recommended for identifying the attribute in each column. Please see Calculated Fields for more information.
    • For Contact Attributes that span multiple record types, please specify the record type within the variable (as in the last example).
  • Examples:
    • {ContactAttribute:Birthday}
    • {ContactAttribute: b51d832d-b358-4250-9abd-e2122d2d422b}
    • {ContactAttribute:StartDate, Staff}
  • Applications: Report, Workflow

Contact Email

• • Format: {ContactEmail:Contact ID or External ID,Email Type}
  • Description: Inserts a contact’s email address. If more than one email address of the same type is marked as “Use”, the first match will be returned. Input the Contact’s external identifier or 36-character GUID, along with the Email Type’s name or external identifier (Personal or Work).
  • Examples:
    • {ContactEmail:{FormAnswer:Name},Work}
    • {ContactEmail:BinghamBrandy53128,Personal}
  • Applications: Form Type

Contact Phone

• • Format: {ContactPhone:Contact ID or External ID,Phone Number Type}
  • Description: Inserts a contact’s phone number. If more than one phone number of the same type is marked as “Use”, the first match will be returned. Input the Contact’s external identifier or 36-character GUID, along with the Phone Number Type’s name or external identifier (Home, Mobile, Work, etc.).
  • Example:
    • {ContactPhone:BinghamBrandy53128,Mobile}
    • {ContactPhone:{FormAnswer:ContactName},Home}
  • Applications: Form Type

County

• • Format: {CountyID}
  • Description: A county within the 50 United States and US territories. No inputs to the variable are necessary.
    • To configure a report filter to select a value from a list of counties, you will need to set the Value field to an ID rather than a name. For example: Address.County ID = {CountyID} will allow you to filter by a single county chosen from the list of US counties.
  • Example: Address.County ID = {CountyID}
  • Applications: Report

Country

• • Format: {CountryID}
  • Description: A country. No inputs to the variable are necessary.
    • To configure a report filter to select a value from a list of countries, you will need to set the Value field to an ID rather than a name. For example: Address.Country ID = {CountryID} will allow you to filter by a single country chosen from the list of all countries.
  • Example: Address.Country ID = {CountryID}
  • Applications: Report

Create Date

• • Format: {CreateDate} or {CreateDate +/- n}
  • Description: The date the form was created. Available only in the Form Name field. Insert a number for the number of days in place of “n”.
  • Example: {CreateDate} or {CreateDate – 2}
  • Applications: Form Type

Current Location

• • Format: {CurrentLocation}
  • Description: Inserts the latitude/longitude coordinates of the user’s location (no inputs necessary). Available only in Form questions when using the Coordinates Data Type.
    • The “current location” is set by the browser.  While questions with this default value can be hidden, they will not work correctly when set to read-only.
  • Example: {CurrentLocation}
  • Applications: Form Type

Current User

• • Format: {CurrentUser} or {CurrentUser:format}
  • Description: The current user of the form or task. This variable accepts the following inputs to format the display name:
    • F – First
    • M – Middle
    • L – Last
    • FL – First Last
    • FML – First Middle Last
    • LF – Last, First
    • LFM – Last, First Middle
  • Examples:
    • {CurrentUser}
    • {CurrentUser:FL}
  • Applications: Document Template, Form Type, Report, Task Type

Date Time

• • Format: {DateTime:<any date or datetime>,<any time or integer representing an hour of the day>}
  • Description: Inserts a date/time value in standard format.
    • The first parameter can be any standard date or date/time value, but if a time is included, it is stripped.
    • The second variable is a time or integer representing an hour of the day.
  • Example: {DateTime:2023-12-30, 14:22} or for APIs: {DateTime:{JsonValue:gmt_datetime},{JsonValue:hour_of_day}}
  • Applications: Scheduled Jobs, Document Template, Form Type, Report, Task Type

Document Attribute

• • Format: {DocumentAttribute:Attribute Type ID or External ID}
  • Description: A value from a document attribute. Insert the Attribute Type’s external identifier or 36-character GUID.
    • This variable will only work in table reports where Document is selected as the Datasource. To use this in a table report, for each column that will have a document attribute, you must select Advanced Features.Calculated Field as the Column field and choose the {DocumentAttribute:} variable in the Calculated Field. Use of the Alias field is highly recommended for identifying the attribute in each column. Please see Calculated Fields for more information.
  • Examples:
    • {DocumentAttribute:Description}
    • {DocumentAttribute: bfeb244f-322b-4abe-bf16-9396e6bcd73c}
  • Applications: Report

End Date

• • Format: {EndDate}
  • Description: The end date in a date range. No inputs to the variable are necessary. The {StartDate} and {EndDate} variables must be applied together; you cannot reference only one of these two variables.
    • When timestamps matter, Assetas recommends using the DateAdd function (please see the example) to add one day to the {EndDate} variable as the timestamp on the {EndDate} variable defaults to 12:00AM (the beginning of the day).
    • If you need to reference a single date, use the {AsOfDate} variable.
    • When configured in a report or document template filter, the combination of {StartDate} and {EndDate} will prompt the user to select a date range prior to running the report.
  • Example:
    • Telemetry.ActiveDate <= DateAdd(day, 1, {EndDate})
    • Date >= {StartDate} AND Date < DateAdd(day, 1, {EndDate})
  • Applications: Document Template, Report

Evaluate

• • Format: {Evaluate:expression}
  • Description: Allows for mathematical functions to be performed on numbers and dates. Please see Evaluate for more information.

    When used in a workflow trigger comparison, where the {Evaluate} function is generating a date, the entire function needs to be surrounded in single quotes: ‘{Evaluate:ToDateTime(…)}’

  • Examples:
    • {Evaluate:{FormAnswer:Count} + 5}
    • {Evaluate: ToDateTime(“{FormAnswer:Date}”).AddDays(10)}
  • Applications: Form Type, Workflow

First Day of the Month

• • Format: {MonthStart} or {MonthStart +/- n}
  • Description: Inserts the first day of the current month. Insert a number for the number of months in place of “n”. Only available when Telemetry Aggregate is selected as the Trigger Type in Workflow.
  • Example: {MonthStart} or {MonthStart – 1}
  • Applications: Workflow

First Day of the Year

• • Format: {YearStart} or {YearStart +/- n}
  • Description: Inserts the first day of the current year. Insert a number for the number of years in place of “n”. Only available when Telemetry Aggregate is selected as the Trigger Type in Workflow.
  • Example: {YearStart} or {YearStart – 1}
  • Applications: Workflow

Form Answer

• • Format: {FormAnswer:Question ID or External ID} or {FormAnswer:Question ID or External ID,format}
  • Description: Answer from a form question. Insert the form question’s external identifier or 36-character GUID. If the form answer contains a contact name, the variable accepts the following inputs to format the display name:
    • F – First
    • M – Middle
    • L – Last
    • FL – First Last
    • FML – First Middle Last
    • LF – Last, First
    • LFM – Last, First Middle
  • Examples:
    • {FormAnswer:Inspector_Name}
    • {FormAnswer:3b06c469-56de-4047-aec1-583d1a77ad95}
    • {FormAnswer:ReportedBy, FL}
  • Applications: Form Type, Report, Workflow

Form Answer Display

• Format: {FormAnswerDisplay:Question ID or External ID}
• Description: Answer from a form question, displayed as text rather than an ID. Insert the form question’s external identifier or 36-character GUID.
  • This is useful when comparing the answer from a previous question’s dropdown list to something else, particularly if the list contains assets or contacts. The form question containing this variable is typically hidden and populated with a Set Answer form rule action.
• Examples:
  • {FormAnswerDisplay:EngineList}
• Applications: Form Type

Form Type

• • Format: {FormType}
  • Description: The current form type of the form being edited (no inputs necessary). Available only in the Form Name field.
  • Example: {FormType}
  • Applications: Form Type

JSON Value

• • Format: {JsonValue:<token>} or {JsonValue:<token>,<Array Index>} or {JsonValue:<token>,<child_token>}
  • Description: For use in API Integration Scheduled Jobs. Returns the value of the given token in the API JSON. Insert the token name and the array index if the data is in an array format. Helpful for performing mathematical functions upon import. Insert the token name and the child token name if the parent token itself contains a JSON object. Base64 encoding will be autodetected and decoded.
  • Example: {JsonValue:serial} or {JsonValue:sensor,2} or {JsonValue:data,date}
  • Applications: Scheduled Job

Last Day of the Month

• • Format: {MonthEnd} or {MonthEnd +/- n}
  • Description: Inserts the last day of the current month. Insert a number for the number of months in place of “n”. Only available when Telemetry Aggregate is selected as the Trigger Type in Workflow.
  • Example: {MonthEnd} or {MonthEnd – 1}
  • Applications: Workflow

Last Day of the Year

• • Format: {YearEnd} Or {YearEnd +/- n}
  • Description: Inserts the last day of the current year. Insert a number for the number of years in place of “n”. Only available when Telemetry Aggregate is selected as the Trigger Type in Workflow.
  • Example: {YearEnd} Or {YearEnd – 1}
  • Applications: Workflow

Last Success Date

• • Format: {LastSuccessDate} or {LastSuccessDate +/- n}
  • Description: Pulls back the start date of the last time the Scheduled Job ran and was successful. Useful for processing deltas in a data set instead of processing the full data set each time a Scheduled Job runs, assuming the data set contains a “last modified date” or something similar. Enter the number of days for n. Fractions are accepted in place of “n”; for example, 0.5 translates to 12 hours.
  • Example: {LastSuccessDate} or {LastSuccessDate – 0.5}
  • Applications: Scheduled Jobs

Manager Of

• • Format:
    • {ManagerOf:Contact ID or External ID}
    • {ManagerOf:Contact ID or External ID,format}
  • Description: The manager of the given contact. The contact must be associated to the manager as a managed contact.
    • Insert the contact’s external identifier or 36-character GUID. Answers to form questions may be nested inside of this variable (please see the examples below).
    • This variable accepts the following inputs to format the display name:
      • F – First
      • M – Middle
      • L – Last
      • FL – First Last
      • FML – First Middle Last
      • LF – Last, First
      • LFM – Last, First Middle
  • Examples:
    • {ManagerOf:BillupsJames27210}
    • {ManagerOf: 3d367a48-8b09-46c7-bd08-95d2763802a2}
    • {ManagerOf:{FormAnswer:EmployeeName}}
    • {ManagerOf:{TriggeringContact},FL}
    • {ManagerOf:{TaskContact:{Triggering Task}},FL}
  • Applications: Form Type, Task Type, Workflow

New Form Link

• • Format: {NewFormLink:<Form Type ID or External ID>,<Link text>, <QuestionID1>=<Value1>,<QuestionID2>=<Value2>, …}
  • Description: Creates a clickable link to another existing form type and allows for custom link text and optional pre-filled default form answers.
  • Examples:
    • {NewFormLink:Storm_CA, Stormwater Corrective Action Report Form}
    • {NewFormLink: 81499d29-a719-4c6e-a722-f564b8673a2b, Incident Follow Up Form}
    • {NewFormLink:EngineForm,Please Complete Engine Form,Attribute1={AssetAttribute:Assetas_EngineDriver},Attribute2={AssetAttribute:Assetas_EngineFuel}}
  • Applications: Form Type, Task Type, Workflow

Now

• • Format: {Now} or {Now +/- n}
  • Description: The current date & time. Insert a number for the number of days in place of “n”.
  • Example: {Now} or {Now + 1}
  • Applications: Document Template, Form Type, Task Type, Workflow
  • This is the preferred default for datetime fields.

Report

• • Format: {ReportID}
  • Description: A report within the database. No inputs to the variable are necessary.
    • Available only when creating a report with the Report Log as the datasource. Using Report.Report ID = {ReportID} as a filter allows for the selection of a report from a list of all available reports.
  • Example: Report.Report ID = {ReportID}
  • Applications: Report

Selection List

• • Format: {SL:ReportID or External ID}
  • Description: An item from a preconfigured Selection List report. Enter the Selection List report’s external identifier or 36-character GUID.
    • To configure a report filter to select a value from an existing Selection List report, you will need to set the Value field to an ID rather than a name. For example: Asset.Asset ID = {SL:ActiveEngines} will allow you to filter by a single item out of the list within the Selection List report.
  • Examples:
    • Asset.Asset ID = {SL:ActiveEngines}
    • Asset.Asset ID = {SL:a01cbd61-dd5b-4770-889c-53d4d84bbc83}
  • Applications: Report

Short Link

• • Format: {ShortURL:<full URL>}
  • Description: This variable converts a full URL into a shortened, 28-character URL Lookup link. This variable is useful for inserting short links in SMS messages. 
  • Examples:
    • {ShortURL: https://app.assetas.com/Asset/Details/a6e818f3-3af0-483b-8411-99ccae77972c}
    • {ShortURL:{NewFormLink:VehicleIncident, New Vehicle Incident Form}}
    • {ShortURL:{TriggeringFormLink}}
  • Applications: Form Type, Task Type, Workflow

Space

• • Format: {Space}
  • Description: Represents a space (not a null). No inputs to the variable are necessary.
  • Examples:
    • {Space}
  • Applications: Report

Start Date

• • Format: {StartDate}
  • Description: The start date in a date range. No inputs to the variable are necessary. The {StartDate} and {EndDate} variables must be applied together; you cannot reference only one of these two variables. If you need to reference a single date, use the {AsOfDate} variable. When configured in a report or document template filter, the combination of {StartDate} and {EndDate} will prompt the user to select a date range prior to running the report.
  • Example: Telemetry.ActiveDate >= {StartDate}
  • Applications: Document Template, Report

State

• • Format: {StateID}
  • Description: A state within the United States or a Canadian province. No inputs to the variable are necessary. To configure a report filter to select a value from a list of states/provinces, you will need to set the Value field to an ID rather than a name. For example: Address.State ID = {StateID} will allow you to filter by a single state/province chosen from the list of all states/provinces.
  • Example: Address.State ID = {StateID}
  • Applications: Report

Task

• • Format: {TaskID}
  • Description: A task. No inputs to the variable are necessary. Only available when Task is selected as the Datasource in a report.
    To configure a report filter to select a value from a list of tasks, you will need to set the Value field to an ID rather than a name. For example: Task.Task ID = {TaskID} will allow you to filter by a task chosen from the list of all available tasks.
  • Example: Task.Task ID = {TaskID}
  • Applications: Report

Task Attribute

• • Format: {TaskAttribute:Attribute Type ID or External ID}
  • Description: The value for a specific task attribute. Enter the Task Attribute Type’s external identifier or 36-character GUID.
  • Examples:
    • {TaskAttribute:Mileage}
    • {TaskAttribute:c6ee6695-a46c-4f31-bfb4-c2517079b232}
  • Applications: Task Type, Report

Task Contact

• • Format:
    • {TaskContact:Task ID or External ID}
    • {TaskContact:Task ID or External ID,format}
  • Description: The contact(s) assigned to the task. Enter the Task’s 36-character GUID. This variable accepts the following inputs to format the display name:
    • F – First
    • M – Middle
    • L – Last
    • FL – First Last
    • FML – First Middle Last
    • LF – Last, First
    • LFM – Last, First Middle
  • Examples:
    • {TaskContact:{TriggeringTask}}
    • {TaskContact: 875487c3-2dc9-4014-f57f-08d8ced07ad1}
    • {TaskContact:{TriggeringTask},FL}
  • Applications: Workflow

Task Details

• • Format: {TaskDetails}
  • Description: The details of the task (includes the link, summary, type, priority, status, due date, and assignees). No inputs to the variable are necessary.
  • Examples:
    • {TaskDetails}
  • Applications: Task Type, Workflow

Task Link

• • Format: {TaskLink}
  • Description: The URL link to the task. No inputs to the variable are necessary.
  • Examples:
    • {TaskLink}
  • Applications: Task Type

Telemetry Average

• • Format: {TelemetryAverage: StartDate=date;EndDate=date;TelemetryType=name, GUID, or EID;UnitOfMeasure=name, GUID, or EID;Rounding=n;AssetID=GUID or AssetAssociationType=ExternalID}
  • Description: Given a telemetry type, unit of measure, and date range, this variable will return the average of all telemetric values matching the criteria where the active date falls within the date range.
    • Within the telemetric variable, please note that the AssetID= argument is optional. If not specified, all telemetry matching the criteria will be included in the variable, regardless of Asset assignment.
    • Telemetric variables may also perform mathematical functions on child records and roll those values up to the parent record by using the AssetAssociationType=<ExternalID> argument, which is optional. This is particularly useful in workflows. In the Workflow Triggers, set an Asset Property Comparison trigger equal to the parent record’s asset type. It is critically important that, when using the AssetAssociationType argument, you set a filter in the Workflow Triggers to only include assets with child records. Otherwise, telemetry values will be set to 0 for all matching assets that don’t have child records.
    • In Reports and Document Templates, you may set AssetID=Asset.AssetID to apply the telemetry variable to each asset returned, individually.
    • Use filters to define to assets to include and apply selection list filters when necessary.
    • In workflows, the triggering asset will automatically be inserted into the telemetric variable, so the specification of the AssetID is not necessary.
    • When using the telemetric variables to evaluate a set of null data, the system will return a null. In workflows, please utilize workflow triggers to avoid evaluating cases where only null data exists.
  • Example: In a report where engines and their attributes are listed, return the average of daily runtime hours by engine over the last week, rounded to the nearest hour: {TelemetryAverage: StartDate={Today – 7}; EndDate={Today}; TelemetryType=Runtime; UnitOfMeasure=hr/day; Rounding=0; AssetID=Asset.AssetID}
  • Applications: Document Template, Report, Workflow

Telemetry Maximum

• • Format: {TelemetryMaximum:StartDate=date;EndDate=date;TelemetryType=name, GUID, or EID;UnitOfMeasure=name, GUID, or EID;Rounding=n;AssetID=GUID or AssetAssociationType=ExternalID}
  • Description: Given a telemetry type, unit of measure, and date range, this variable will return the maximum of all telemetric values matching the criteria where the active date falls within the date range.
    • Within the telemetric variable, please note that the AssetID= argument is optional. If not specified, all telemetry matching the criteria will be included in the variable, regardless of Asset assignment.
    • Telemetric variables may also perform mathematical functions on child records and roll those values up to the parent record by using the AssetAssociationType=<ExternalID> argument, which is optional. This is particularly useful in workflows. In the Workflow Triggers, set an Asset Property Comparison trigger equal to the parent record’s asset type. It is critically important that, when using the AssetAssociationType argument, you set a filter in the Workflow Triggers to only include assets with child records. Otherwise, telemetry values will be set to 0 for all matching assets that don’t have child records.
    • In Reports and Document Templates, you may set AssetID=Asset.AssetID to apply the telemetry variable to each asset returned, individually.
    • Use filters to define to assets to include and apply selection list filters when necessary.
    • In workflows, the triggering asset will automatically be inserted into the telemetric variable, so the specification of the AssetID is not necessary.
    • When using the telemetric variables to evaluate a set of null data, the system will return a null. In workflows, please utilize workflow triggers to avoid evaluating cases where only null data exists.
  • Example: Maximum precipitation over the last five days, rounded to the nearest tenth of an inch:  {TelemetryMaximum: StartDate={Today – 5}; EndDate={Today}; TelemetryType=Precipitation; UnitOfMeasure=in; Rounding=1; AssetID=Asset.AssetID}
  • Applications: Document Template, Report, Workflow

Telemetry Minimum

• • Format: {TelemetryMinimum:StartDate=date;EndDate=date;TelemetryType=name, GUID, or EID;UnitOfMeasure=name, GUID, or EID;Rounding=n;AssetID=GUID or AssetAssociationType=ExternalID}
  • Description: Given a telemetry type, unit of measure, and date range, this variable will return the minimum of all telemetric values matching the criteria where the active date falls within the date range.
    • Within the telemetric variable, please note that the AssetID= argument is optional. If not specified, all telemetry matching the criteria will be included in the variable, regardless of Asset assignment.
    • Telemetric variables may also perform mathematical functions on child records and roll those values up to the parent record by using the AssetAssociationType=<ExternalID> argument, which is optional. This is particularly useful in workflows. In the Workflow Triggers, set an Asset Property Comparison trigger equal to the parent record’s asset type. It is critically important that, when using the AssetAssociationType argument, you set a filter in the Workflow Triggers to only include assets with child records. Otherwise, telemetry values will be set to 0 for all matching assets that don’t have child records.
    • In Reports and Document Templates, you may set AssetID=Asset.AssetID to apply the telemetry variable to each asset returned, individually.
    • Use filters to define to assets to include and apply selection list filters when necessary.
    • In workflows, the triggering asset will automatically be inserted into the telemetric variable, so the specification of the AssetID is not necessary.
    • When using the telemetric variables to evaluate a set of null data, the system will return a null. In workflows, please utilize workflow triggers to avoid evaluating cases where only null data exists.
  • Example: In a report where wells and their attributes are listed, return the minimum barrels of oil produced per month over the last year by well, rounded to the nearest barrel: {TelemetryMinimum: StartDate={Today – 365}; EndDate={Today}; TelemetryType=Produced Oil; UnitOfMeasure=bbl/month; Rounding=0; AssetID=Asset.AssetID}
  • Applications: Document Template, Report, Workflow

Telemetry Summation

• • Format: {TelemetrySum:StartDate=date;EndDate=date;TelemetryType=name, GUID, or EID;UnitOfMeasure=name, GUID, or EID;Rounding=n;AssetID=GUID or AssetAssociationType=ExternalID}
  • Description: Given a telemetry type, unit of measure, and date range, this variable will return the summation of all telemetric values matching the criteria where the active date falls within the date range.
    • Within the telemetric variable, please note that the AssetID= argument is optional. If not specified, all telemetry matching the criteria will be included in the variable, regardless of Asset assignment.
    • Telemetric variables may also perform mathematical functions on child records and roll those values up to the parent record by using the AssetAssociationType=<ExternalID> argument, which is optional. This is particularly useful in workflows. In the Workflow Triggers, set an Asset Property Comparison trigger equal to the parent record’s asset type. It is critically important that, when using the AssetAssociationType argument, you set a filter in the Workflow Triggers to only include assets with child records. Otherwise, telemetry values will be set to 0 for all matching assets that don’t have child records.
    • In Reports and Document Templates, you may set AssetID=Asset.AssetID to apply the telemetry variable to each asset returned, individually.
    • Use filters to define to assets to include and apply selection list filters when necessary.
    • In workflows, the triggering asset will automatically be inserted into the telemetric variable, so the specification of the AssetID is not necessary.
    • When using the telemetric variables to evaluate a set of null data, the system will return a null. In workflows, please utilize workflow triggers to avoid evaluating cases where only null data exists.
  • Example A: In a workflow with a triggering engine, the sum of the operating hours since the last oil change date by engine: {TelemetrySum: StartDate={AssetAttribute:LastOilChangeDate}; EndDate={Today}; TelemetryType=Runtime; UnitOfMeasure=hr/day; Rounding=0, AssetID=Asset.AssetID}
  • Example B: In a workflow with a triggering asset type of facility, sum the gas production from three months ago at the underlying wells to the facility level: {TelemetrySum: StartDate={MonthStart – 3}; EndDate={MonthEnd – 3}; TelemetryType=ProducedGas; UnitOfMeasure=mscf/month; Rounding=3; AssetAssociationType=Assetas_PhysicalLocation}
  • Applications: Document Template, Report, Workflow

Telemetry Type

• • Format: {TelemetryTypeID}
  • Description: A telemetry type. No inputs to the variable are necessary. Only available when Telemetry is selected as the Datasource in a report. To configure a report filter to select a value from a list of telemetry types, you will need to set the Value field to an ID rather than a name. For example: Telemetry Type.Telemetry Type ID = {TelemetryTypeID} will allow you to filter by a telemetry type chosen from the list of all available telemetry types.
  • Example: Telemetry Type.Telemetry Type ID = {TelemetryTypeID}
  • Applications: Report

Timestamp ID

• • Format: {TimestampID} or {TimestampID:YYMMDD.HHMMSS}
  • Description: Creates a unique 12-character identifier that combines the current date and time in the following formats:
    • {TimestampID} returns YYMMDDHHMMSS
    • {TimestampID:YYMMDD.HHMMSS} returns YYMMDD.HHMMSS
    • Useful in creating unique identifiers or case numbers in forms that are easily sortable. Assetas recommends using the ‘Read Only’ form question toggle in conjunction with this variable to prevent manipulation of the unique identifier.
  • Examples:
    • {TimestampID}
    • {TimestampID:YYMMDD.HHMMSS}
  • Applications: Form Type

Today

• • Format: {Today} Or {Today +/- n}
  • Description: The current date in your timezone. Insert a number for the number of days in place of “n”.
  • Example: {Today}
  • Applications: Document Template, Form Type, Report, Task Type, Workflow
  • This is the preferred default for date fields.
    • Applying the “today” variable to a datetime field will result in the current time in UTC.

Triggering Active Date

• • Format: {TriggeringActiveDate}
  • Description: For use with the Telemetry Comparison trigger. Inserts the active date of the telemetry that triggered the workflow. No inputs to the variable are necessary.
  • Example: {TriggeringActiveDate}
  • Applications: Workflow

Triggering Asset

• • Format: {TriggeringAsset}
  • Description: The name of the asset(s) that caused the workflow triggers to evaluate to ‘True’. No inputs to the variable are necessary.
  • Example: {TriggeringAsset}
  • Applications: Workflow

Triggering Asset ID

• • Format: {TriggeringAssetID}
  • Description: The GUID of the asset(s) that caused the workflow triggers to evaluate to ‘True’. No inputs to the variable are necessary. If passing this variable into an email or SMS notification, we recommend toggling the Summary Email/SMS option to ‘off’.
  • Example: {TriggeringAssetID}
  • Applications: Workflow

Triggering Asset Link

• • Format: {TriggeringAssetLink}
  • Description: A link with the name of the asset(s) that caused the workflow triggers to evaluate to ‘True’. No inputs to the variable are necessary.
  • Example: {TriggeringAssetLink}
  • Applications: Workflow

Triggering Contact

• • Format: {TriggeringContact} or {TriggeringContact:}
  • Description: The name of the contact(s) that caused the workflow triggers to evaluate to ‘True’. This variable accepts the following inputs to format the display name:
    • F – First
    • M – Middle
    • L – Last
    • FL – First Last
    • FML – First Middle Last
    • LF – Last, First
    • LFM – Last, First Middle
  • Examples:
    •  {TriggeringContact}
    • {TriggeringContact:FL}
  • Applications: Workflow

Triggering Form

• • Format: {TriggeringForm}
  • Description: The 36-character GUID of the form(s) that caused the workflow triggers to evaluate to ‘True’. No inputs to the variable are necessary.
  • Example: {TriggeringForm}
  • Applications: Workflow

Triggering Form Link

• • Format: {TriggeringFormLink}
  • Description: A link with the name of the form(s) that caused the workflow triggers to evaluate to ‘True’, or the form from where the notification originated. No inputs to the variable are necessary.
  • Example: {TriggeringFormLink}
  • Applications: Form Type, Workflow

Triggering Group Active Date

• • Format: {TriggeringGroupActiveDate}
  • Description: For use with the Telemetry Aggregate trigger. The triggering group’s active date, from the Telemetry Aggregate trigger, based on the Date Grouping selection. For example, if the Date Grouping is Monthly, the active date will be set to the first day of the month. No inputs to the variable are necessary.
  • Example: {TriggeringGroupActiveDate}
  • Applications: Workflow

Triggering Group Inactive Date

• • Format: {TriggeringGroupInactiveDate}
  • Description: For use with the Telemetry Aggregate trigger. The triggering group’s inactive date, from the Telemetry Aggregate trigger, based on the Date Grouping selection. For example, if the Date Grouping is Monthly, the inactive date will be set to the last day of the month. No inputs to the variable are necessary.
  • Example: {TriggeringGroupInactiveDate}
  • Applications: Workflow

Triggering Inactive Date

• • Format: {TriggeringInactiveDate}
  • Description: For use with the Telemetry Comparison trigger. Inserts the inactive date of the telemetry that triggered the workflow. No inputs to the variable are necessary.
  • Example: {TriggeringInactiveDate}
  • Applications: Workflow

Triggering Max Active Date

• • Format: {TriggeringMaxActiveDate}
  • Description: For use with the Telemetry Comparison trigger. Inserts the maximum active date of the telemetry that triggered the workflow. No inputs to the variable are necessary.
  • Example: {TriggeringMaxActiveDate}
  • Applications: Workflow

Triggering Max Inactive Date

• • Format: {TriggeringMaxInactiveDate}
  • Description: For use with the Telemetry Comparison trigger. Inserts the maximum inactive date of the telemetry that triggered the workflow. No inputs to the variable are necessary.
  • Example: {TriggeringMaxInactiveDate}
  • Applications: Workflow

Triggering Min Active Date

• • Format: {TriggeringMinActiveDate}
  • Description: For use with the Telemetry Comparison trigger. Inserts the minimum active date of the telemetry that triggered the workflow. No inputs to the variable are necessary.
  • Example: {TriggeringMinActiveDate}
  • Applications: Workflow

Triggering Min Inactive Date

• • Format: {TriggeringMinInactiveDate}
  • Description: For use with the Telemetry Comparison trigger. Inserts the minimum inactive date of the telemetry that triggered the workflow. No inputs to the variable are necessary.
  • Example: {TriggeringMinInactiveDate}
  • Applications: Workflow

Triggering Task

• • Format: {TriggeringTask}
  • Description: The 36-character GUID of the task(s) that caused the workflow triggers to evaluate to ‘True’. No inputs to the variable are necessary.
  • Example: {TriggeringTask}
  • Applications: Workflow

Triggering Telemetry Average

• • Format: {TriggeringAvgNumericValue}
  • Description: For use with the Telemetry Aggregate trigger. Inserts the average of the telemetry values, based on the Date Grouping in the Telemetry Aggregate trigger, over the specified date range. No inputs to the variable are necessary.
  • Example: {TriggeringAvgNumericValue}
  • Applications: Workflow

Triggering Telemetry Sum

• • Format: {TriggeringSumNumericValue}
  • Description: For use with the Telemetry Aggregate trigger. Inserts the sum of the telemetry values, based on the Date Grouping in the Telemetry Aggregate trigger, over the specified date range. No inputs to the variable are necessary.
  • Example: {TriggeringSumNumericValue}
  • Applications: Workflow

Triggering Telemetry Value

• • Format: {TriggeringNumericValue}
  • Description: For use with the Telemetry Comparison trigger. Inserts the value of the telemetry that triggered the workflow. No inputs to the variable are necessary.
  • Example: {TriggeringNumericValue}
  • Applications: Workflow

Unit of Measure

• • Format: {UnitOfMeasureID}
  • Description: A unit of measure. No inputs to the variable are necessary. Only available when Telemetry is selected as the Datasource in a report. To configure a report filter to select a value from a list of units of measure, you will need to set the Value field to an ID rather than a name. For example: Unit of Measure.Unit of Measure ID = {UnitOfMeasureID} will allow you to filter by a unit of measure chosen from the list of all available units of measure.
  • Examples:
    • Unit of Measure.Unit of Measure ID = {UnitOfMeasureID}
  • Applications: Report