The Webex Location Node Mapping menu (data/WebexLocationNodeMapping) allows for the mapping of an existing VOSS Automate intermediate hierarchy node to a Webex location name. This feature allows administrators to sort the Webex locations into business driven logical groupings. Note that the mapping of the Webex location name must be in place before the locations are synced from control hub. If the location match string is not found, a new location will be built directly under the customer node. Should a mapping be missing, an administrator may purge that location data, create the mapping in Webex Location Node Mapping and run the data sync again.

Upon data sync, Webex locations that match the Search String are then moved under the Intermediate node.

Important

The text entered into the Search String field:

can be case-insensitive
should be contained in the Webex location name as uniquely as possible, to exclude unwanted location name matches
matching operator is containsIgnoreCase

Upon the next Webex data sync, Webex locations matching the Search String will be moved under the selected Intermediate Node.

Model Details: data/WebexLocationNodeMapping

An asterisk * in the title indicates the field is mandatory.
If a field has a default value, it is shown in the Description column.
If the field type is an array, the Field Name has a .[n] suffix, where n is the array index placeholder.
Object and array field names are listed to provide context. If a field belongs to an object or an array, the full field name is shown in dot separated notation.

Title															Description																				Details
Intermediate Node																																			Field Name: IntermediateNode Type: String
Search String																																			Field Name: searchString Type: String

Model: data/WebexLocationNodeMapping

Webex Location Node Mapping

Model Details: data/WebexLocationNodeMapping