System Variables - Specific To System SettingsParameters - 1-30-2019
System Variables - Specific To System SettingsParameters - 1-30-2019
Automation Anywhere and the Automation Anywhere logo are trademarks owned by Automation Anywhere
Software,
The information contained in this documentation is proprietary and confidential.Your use of this information and
Automation Anywhere Software products is subject to the terms and conditions of the applicable End-User
License Agreement and/or Nondisclosure Agreement and the proprietary and restricted rights notices included
therein.
You may print, copy, and use the information contained in this documentation for the internal needs of your
user base only. Unless otherwise agreed to by Automation Anywhere and you in writing, you may not otherwise
distribute this documentation or the information contained here outside of your organization without obtaining
Automation Anywhere’s prior written consent for each such distribution.
Contents
System Variables - Specific to System Settings/Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
The variables return actual system settings and parameters, such as RAM, CPU/RAM usage, and total
RAM.
Note: When you select the System variable, a menu is displayed from which you can select the
specific system variable (see steps below).
Note: Don't confuse System Related Variables with System Variables. To select System
from System Related Variables, refer the following section.
2. Select System and click Insert, a pop up window for System Variable Option is displayed.
Troubleshooting an error
Error: If you use the $CPUUsage$ variable in a message box and an error message is issued, you need
to reset the counter for the system by performing the following action:
Open a command prompt and enter the following two commands:
cd\windows\system32 [enter]
lodctr /R [enter]
Examples
When creating an executable file (EXE) for a task, you might want to use the path of the EXE to log a file
or refer to a file located in a folder. In this case, use the AAApplicationPath variable to select the path of
the EXE from any location in which it is stored. This eliminates the need to use static paths for EXEs.
1. The following command stores the current application path in a log file. Drag and drop a Log To File
command to your task, and press the F2 key to insert $AAApplicationPath$ variable:
Log to File:Automation Anywhere Application Path:$AAApplicationPath$ in "C:\Variable
2. The following command stores the current RAM usage and CPU usage in a log file. Drag and drop a
Log To File command to your task, and press the F2 key to insert $RAMUsage$ and $CPUUsage$
variables.
Log to File: CPU Usage:$CPUUsage$RAM Usage:$RAMUsage$ in "C:\Variable Operation.txt"
3. The following command stores the current Task path in a log file. Drag and drop a Log To File
command to your task, and press the F2 key to insert $AATaskName$ variable.
Log to File:Automation Anywhere Application Path:$AATaskName$ in "C:\Variable Operati