Skip to content
This repository was archived by the owner on Sep 2, 2025. It is now read-only.

Commit 5e8c96f

Browse files
Merge pull request #1575 from cmillane-splunk/patch-4
Update servicenow-integration.rst
2 parents 0f5fbb0 + b197867 commit 5e8c96f

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

sp-oncall/spoc-integrations/servicenow-integration.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ You can do the following with the integration:
2626
Requirements
2727
=====================
2828

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
3030
* ServiceNow account: Requires ServiceNow Administrative Privileges to create the application registry and an Active, Web Service Access only user with the ITIL role.
3131
* Splunk On-Call version required: Enterprise level of service
3232

@@ -125,7 +125,7 @@ Preconfigured fields that are immediately available are:
125125
* assigned_to
126126
* resolved_by
127127

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.
129129

130130
The following fields are automatically handled by the integration mapping:
131131

@@ -161,7 +161,7 @@ Only some fields are preconfigured with the VictorOps app, so mapping additional
161161
#. Last, make sure the 2 fields are mapped,in the :guilabel:`Field Map` field.
162162
#. Select :guilabel:`Save`.
163163

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>``.
165165

166166
In the following example image, the field value on the Splunk On-Call import table in ServiceNow is ``victorops_custom_field``.
167167

0 commit comments

Comments
 (0)