Contents
Introduction
To use scope you must define an expression, read using scope and filter expressions for more information.
On this page:
Available scope attributes
The system has a number of predefined attributes for use in a scope expression.
| Type | Name |
|---|---|
| Predefined attribute | ostype |
| osver | |
| name | |
| rammb | |
| devicetype | |
| osvertxt | |
| agentver | |
| vrplatform | |
| model | |
| fqdn | |
| devtype | |
| timezone | |
| lastboot | |
| tagtxt | |
| managementgroup |
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": "tagtext",
"Operator": "",
"Value": "key = value"
}
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"
}