[GH-ISSUE #568] BUG: Checks not passing value properly #361

New issue

Closed

opened 2026-03-02 02:15:47 +03:00 by kerem · 3 comments

kerem commented

2026-03-02 02:15:47 +03:00

Owner

Originally created by @ghosty212 on GitHub (Jun 11, 2021).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/568

Originally assigned to: @wh1te909 on GitHub.

Server Info (please complete the following information):

OS: Ubuntu 20.04
Browser: chrome
RMM Version (as shown in top left of web UI): 0.6.13

Installation Method:

[X ] Standard

Agent Info (please complete the following information):

Agent version (as shown in the 'Summary' tab of the agent from web UI): 1.5.7
Agent OS: Windows 10 Pro, 64 bit v2009 (build 19042.1052)

Describe the bug
Script Variables cannot be used in script checks. Using {{agent.name}} or {{site.name}} in a script check leads to the variable being {agent.name} or {site.name} instead of the actual agent.name or site.name. Same for custom fields.

To Reproduce
Steps to reproduce the behavior:
1.

# Test-CustomField.ps1

param (
   [string] $ClientName,
)

Write-Output "Client: $ClientName"

add Test-CustomField.ps1 as script check with variable ( -ClientName {{client.name}} )
run check
see that output is: Client: {client.name}

Expected behavior
Output should be the actual value of client.name. Like it is when running the script via "run script" or as automated task.

Additional context
there was a similiar bug with automated tasks before and fixed in #514

Originally created by @ghosty212 on GitHub (Jun 11, 2021). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/568 Originally assigned to: @wh1te909 on GitHub. **Server Info (please complete the following information):** - OS: Ubuntu 20.04 - Browser: chrome - RMM Version (as shown in top left of web UI): 0.6.13 **Installation Method:** - [X ] Standard **Agent Info (please complete the following information):** - Agent version (as shown in the 'Summary' tab of the agent from web UI): 1.5.7 - Agent OS: Windows 10 Pro, 64 bit v2009 (build 19042.1052) **Describe the bug** Script Variables cannot be used in script checks. Using {{agent.name}} or {{site.name}} in a script check leads to the variable being {agent.name} or {site.name} instead of the actual agent.name or site.name. Same for custom fields. **To Reproduce** Steps to reproduce the behavior: 1. ``` # Test-CustomField.ps1 param ( [string] $ClientName, ) Write-Output "Client: $ClientName" ``` 2. add Test-CustomField.ps1 as script check with variable ( -ClientName {{client.name}} ) 3. run check 4. see that output is: `Client: {client.name}` **Expected behavior** Output should be the actual value of client.name. Like it is when running the script via "run script" or as automated task. **Additional context** there was a similiar bug with automated tasks before and fixed in #514