Rule Synopsis
These are the rule/s that determine how Azure Status values are mapped and transformed into the four different sets of ServiceNow Status values.
Rule Details and Default
The rule/s are described by the mapping table (called a “value map”) shown below.
|
AWS Status Values
|
|
ServiceNow Hardware Status |
ServiceNow Hardware Sub-Status |
ServiceNow Install Status |
ServiceNow Operational Status |
|||||
|
Value |
Label |
|
Value |
Label |
Value |
Label |
Value |
Label |
Value |
Label |
|
1 |
|
-> |
installed |
Installed |
in_use |
In Use |
1 |
Installed |
1 |
Operational |
|
-1
|
|
-> |
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 Azure deleted IT Resource.
Override Options
Context
Customers may consider changing the mapping of individual Azure Status values to change the resulting ServiceNow status values. This may be required to meet the requirements of a customer specific instance of ServiceNow (i.e. to ensure the Status values operate correctly for your business processes/workflows).
Options
-
The transformation of the incoming Azure status value into each of the four ServiceNow status values can be amended.
Overriding via Connection Settings
N/A
Additional Information
N/A
Related Rules
Support Model for Rule Overrides
Question: Can overrides be performed by customers without a Syncfish Extended Implementation and Support Plan?
Answer: No (a plan is needed - see below)
Question: Which Syncfish Extended Implementation and Support Plan is required to obtain overrides of this rule
Answer: Either a Bronze Plan, Silver Plan or Gold Plan