Remote Agent Context Variables

The Remote Agent Context Variables can be used in Event Rules, such as Remote Agent template name, status, last update, and so on.

Each of the variables is described below. For more information about using context variables in EFT, refer to EFT Context Variables (List).

Text Displayed



Remote Agent Name


Computer name of remote system running the Remote Agent, enumerated if there is more than one Agent with that name.


Remote Agent Version


Version of Remote Agent update

Remote Agent Last Update Time Stamp


Date of last Remote Agent update

Remote Agent Next Update Time Stamp


Date of next scheduled Remote Agent update

Remote Agent NetBIOS Name


Computer name of remote system running the agent

Remote Agent Template


Template name associated with the Agent

Remote Agent Status


Status of Remote Agent (for example, Active, Pending, Approved, Denied, Banned)

RAM Environment Variables

The RAM can make use of environment variables in RAM Event Rules.

  • When %ENV.[value]% is used in event rules, EFT will look up the “value” portion from the systems environment variables

  • If “ENV.” does not precede the value, then it is not an event rule context variable

  • ENV.<variable> can be almost anything. In addition to system variables such as "ENV.OS" you can make up your own variables. In the example below, a file is copied to another server with the type of operating system (OS) prepended to the front of the file name.

Remote Agent Event Rule Condition

You can add a "If using Remote Agent does/does not equal to yes/no" to EFT Event Rules for the following events:

  • File Uploaded

  • File Downloaded

  • File Upload Failed

  • File Download Failed

  • Before Download

This Condition works for HTTP and HTTPS interactions only.