You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 2, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: sp-oncall/spoc-integrations/servicenow-integration.rst
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ You can do the following with the integration:
26
26
Requirements
27
27
=====================
28
28
29
-
* ServiceNow versions supported: Madrid, New York, Orlando, Paris, Quebec, Rome, San Diego, Tokyo, Utah
29
+
* ServiceNow versions supported: Madrid, New York, Orlando, Paris, Quebec, Rome, San Diego, Tokyo, Utah, Vancouver, Washington DC, Xanadu
30
30
* ServiceNow account: Requires ServiceNow Administrative Privileges to create the application registry and an Active, Web Service Access only user with the ITIL role.
31
31
* Splunk On-Call version required: Enterprise level of service
32
32
@@ -125,7 +125,7 @@ Preconfigured fields that are immediately available are:
125
125
* assigned_to
126
126
* resolved_by
127
127
128
-
You can set all the preconfigured fields using the rules engine using the followig syntax: ``ServiceNowField_victorops\_<field_name>``.
128
+
You can set all the preconfigured fields using the rules engine using the following syntax: ``ServiceNowField_victorops\_<field_name>`` or ``ServiceNowField_u_victorops\_<field_name>``. The particular syntax will depend on the specific ServiceNow environment version and may require testing.
129
129
130
130
The following fields are automatically handled by the integration mapping:
131
131
@@ -161,7 +161,7 @@ Only some fields are preconfigured with the VictorOps app, so mapping additional
161
161
#. Last, make sure the 2 fields are mapped,in the :guilabel:`Field Map` field.
162
162
#. Select :guilabel:`Save`.
163
163
164
-
Now you can use the Splunk On-Call alert rules engine to supply the field values with the same syntax as before: set ``ServiceNowField_<field_name>`` to new value ``<value>``.
164
+
Now you can use the Splunk On-Call alert rules engine to supply the field values with the same syntax as before: set ``ServiceNowField_<field_name>`` OR ``ServiceNowField_u_victorops\_<field_name>`` (depending on ServiceNow version) to new value ``<value>``.
165
165
166
166
In the following example image, the field value on the Splunk On-Call import table in ServiceNow is ``victorops_custom_field``.
0 commit comments