Security Compliance

Script parameters for group membership and file server alerts not working in ARM

This article describes a known issue in ARM where certain scripting parameters for group membership and file server change alerts do not work as expected. This article also provides a functional workaround.

First published date

12/4/2025 12:26 PM

Last published date

12/4/2025 4:09 PM

Overview

In ARM Configuration, users can add scripts to run before or after some changes. The same applies to alerts; when an alert triggers, it will run an external script. You can configure it in ARM Configuration > Scripting > Alerts. ARM also provides several built-in parameters that can be passed to the script.

Due to a known product issue, some parameters displayed in the UI are currently not functioning. Examples include:

  • {AddedMemberAccounts->AccountClass}
  • {AddedMemberAccounts->Count}

This behavior also affects scripting for file server change alerts.

Product section

Access Rights Manager

Cause

This issue is caused by a known issue in the ARM product, where certain script parameters shown in the UI are not correctly mapped or passed to the script engine.

Resolution

Use the following parameter replacements:

 

Instead of using the following parameters from UI:Use:
{AddedMemberAccounts->AccountClass}{AddedMemberAccounts->AccountDetails0->AccountClass}
{AddedMemberAccounts->Provider}{AddedMemberAccounts->AccountDetails0->Provider}
{AddedMemberAccounts->LoginName}{AddedMemberAccounts->AccountDetails0->LoginName}
{AddedMemberAccounts->DisplayName}{AddedMemberAccounts->AccountDetails0->DisplayName}
{AddedMemberAccounts->SecurityIdentifier}{AddedMemberAccounts->AccountDetails0->SecurityIdentifier}
{AddedMemberAccounts->FullName}{AddedMemberAccounts->AccountDetails0->FullName}
{AffectedPath->AccountClass}{AffectedPath->AccountDetails0->AccountClass}
{AffectedPath->Provider}{AffectedPath->AccountDetails0->Provider}
{AffectedPath->LoginName}{AffectedPath->AccountDetails0->LoginName}
{AffectedPath->DisplayName}{AffectedPath->AccountDetails0->DisplayName}
{AffectedPath->SecurityIdentifier}{AffectedPath->AccountDetails0->SecurityIdentifier}
{AffectedPath->FullName}{AffectedPath->AccountDetails0->FullName}
{AddedMemberAccounts->AccountClass}{AddedMemberAccounts->AccountDetails0->AccountClass}
{AddedMemberAccounts->Provider}{AddedMemberAccounts->AccountDetails0->Provider}
{AddedMemberAccounts->LoginName}{AddedMemberAccounts->AccountDetails0->LoginName}
{AddedMemberAccounts->DisplayName}{AddedMemberAccounts->AccountDetails0->DisplayName}
{AddedMemberAccounts->SecurityIdentifier}{AddedMemberAccounts->AccountDetails0->SecurityIdentifier}
{AddedMemberAccounts->FullName}{AddedMemberAccounts->AccountDetails0->FullName}
{AffectedPath->AccountClass}{AffectedPath->AccountDetails0->AccountClass}
{AffectedPath->Provider}{AffectedPath->AccountDetails0->Provider}
{AffectedPath->LoginName}{AffectedPath->AccountDetails0->LoginName}
{AffectedPath->DisplayName}{AffectedPath->AccountDetails0->DisplayName}
{AffectedPath->SecurityIdentifier}{AffectedPath->AccountDetails0->SecurityIdentifier}
{AffectedPath->FullName}{AffectedPath->AccountDetails0->FullName}

 

Note:

  • The SolarWinds development team is actively working on a fix for this issue.
  • If the workaround does not resolve your situation, please open a case with SolarWinds Technical Support for further investigation and escalation if necessary