Rule 5 - Mapping of Meraki Status Values to ServiceNow Status Values

Rule Synopsis

These are the rule/s that determine how Meraki Status values are mapped and transformed into the four different sets of ServiceNow Status values.

Rule Details and Default

By default, CI Sync sets the various ServiceNow status values according to the mapping table (called a “value map”) shown below.

Meraki Status Values (Single Set of Values only)			ServiceNow Hardware Status		ServiceNow Hardware Sub-Status		ServiceNow Install Status		ServiceNow Operational Status
Value	Label		Value	Label	Value	Label	Value	Label	Value	Label
1	Active	->	installed	Installed	in_use	In Use	1	Installed	1	Operational
-1 (See Note)		->	retired	Retired	divested	Divested	7	Retired	6	Retired
Otherwise		->							5	Ready

Note: CI Sync internally uses a logical value of minus one (-1) to represent an Meraki deleted asset (i.e. assets no longer visible to CI Sync).

Override Options

Context

Customers may consider changing how CI Sync sets the various ServiceNow status values to meet their CI and Asset lifecycle management requirements within ServiceNow.

Options

The transformation of the incoming Meraki status value into each of the four ServiceNow status values can be amended.

Overriding via Connection Settings

Not Available - Requires a Custom Data Sync Rule (and therefore a Syncfish Support Plan to modify the default behaviour)

Additional Information

N/A