Skip to main content

1E 8.1 (on-premises)

Defining the scope

To use scope you must define an expression, readUsing scope and filter expressionsfor more information.

Available scope attributes

The system has a number of predefined attributes for use in a scope expression.

Type

Name

Attribute

ostype

osver

name

rammb

osvertxt

agentver

vrplatform

model

fqdn

devtype

timezone

lastboot

tagtxt

managementgroup

criticality

Scope expression limitations pre v3.2

The two scope expression limitations for Tachyon pre v3.2 are the:

  • Only operator supported in the expression tree object is AND

  • System only supports single level expression trees, for example you cannot have an expression tree object and an operand for another expression tree object.

Handling tags

Tags are a specific case. Tags always use the tagtxt attribute name.

To scope on tags leave the Operator field blank (""), like:

Tag element Json

{
        "Attribute": "tagtxt",
        "Operator": "",
        "Value": "key=value"
}

Note

Tag names are not case-sensitive but tag values are, so you will get an error if you specify a tag value whose case does not match one of the stored values defined for that tag.

Also there cannot be spaces around the = sign, if you specify "key = value" then you will get an error

Handling Management Groups

Management groups are another special case. They always use the managementgroup attribute name.

The only operator they support is == and do not have a data type.

The value is the UsableId, not the Name or Id of the Management group.

Tag element Json

{
        "Attribute": "managementgroup",
        "Operator": "==",
        "Value": "40497EF0F9C344BE937E2813D22457E9"
}
Handling Criticality

When criticality is used in a scope expression the value needs to be the numerical value, not the "friendly" name seen in the UI.

Mapping between the numbers and names can be found in the database in the GlobalSettings table, row with the name "CriticalityMapping".

The default mapping can be seen below.

Note

Double check these mappings as they might have been changed in your installation of Tachyon.

Numerical Value

Friendly name

0

Undefined

1

Non-critical

2

Low

3

Medium

4

High

5

Critical