---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Define temporary variables for a pattern allowlist

# Define temporary variables for a pattern allowlist {#ariaid-title1}

* Release version: Yokohama
* 
* Updated December 7, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Define temporary variables by assigning values such as executable paths, config file paths, and so forth. Defining temporary variables ensures that runtime commands are successful.

## About this task

If a Linux command executable relies on an undefined temporary variable, the command fails at runtime.

For example, for the command `$pathToCmd "/log/acc.log"`, if a value is not defined for `$pathToCmd`, the command will fail.

## Before you begin

Role required: agent_client_collector_admin

## Procedure

1. Navigate to AllPattern DesignerPattern Allowlist Temporary Variables.
2. Select New to create a new variable.
3. Create a record and define the temporary variable.  
   For example:
   {#define-temp-variables__table_ect_znc_4hc__entry__2}

   | Field | Value |
   |-|-|
   | Value | bin/sh/testexec |
   | Pattern | .NET Application |
   | Operating system | Linux |
   | Temporary variable | exePath |
   [Table 1. Pattern Allowlist Temporary Variables]

   {#define-temp-variables__table_ect_znc_4hc}
4. Select Submit.

*[\>]: and then