Script variables, targets and schedules
Secret and platform variables, running as the signed-in user, categories that limit who runs a script, running on a site or customer, and scheduled scripts.
Updated
These build on Scripts. Everything a version needs (its parameters, how it runs) is part of what the approver signs with their passkey; the values people type are not, so an approved version runs with any valid values.
Variables
Add parameters when you save a version. Each arrives in the script as an environment variable, REVO_ARG_<NAME>.
| Type | When it runs |
|---|---|
| Text, whole number, yes or no, one of a list | Asked when someone runs the script or sets up a schedule. Add a question to make the prompt clear. |
| Secret (masked) | Typed in a password field. The value travels only inside the signed job, which is kept encrypted; run history shows ********. A script with a secret parameter doesn't send back what it printed, so the secret can't leak through its output. Its exit code still comes back. Needs RevoAgent 0.11. |
| From the device or customer | Filled per device when the job is signed: the device's name, hostname, operating system, serial number or local IP address, its customer's name or ID, or its site's name or ID. Nobody types it. |
Run as the signed-in user
A version can run as the person signed in at the device's console instead of the system account: useful for settings in the user's own profile. It needs RevoAgent 0.11 on Windows or macOS (not Linux). If nobody is signed in, the device reports that instead of running it.
Categories
Settings → Scripts → Categories groups scripts. A category can limit who runs its scripts to admins, technicians or both; owners always can. Pick a script's category on its page.
Targets
Run a script on devices you pick, every device at a site, every device of a customer, or every device. A site, a customer or every device is counted when the run starts, and always asks you to type the script's name. Your role's limit still applies: technicians run on up to 25 devices at a time, owners and admins on up to 500. For more, run it per customer or site.
Schedules
On a script's page, Schedule runs an approved version once later, or every 15 minutes up to every 12 months, in your time zone. Choose what happens to devices that are offline when it runs: run when they come back (within seven days), or skip them that time.
A schedule runs with the rights of the person who last saved it, checked at every run. If that person loses the right to run scripts or leaves, the schedule stops and says why; someone else can take it over by saving it.
Scheduled scripts stop when scripts are paused for the workspace. To pause only one customer's scheduled scripts, use the switch at the top of that customer's Scripts page; manual runs still work. Only an owner or admin turns them back on.