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

Commit e2a9561

Browse files
Merge pull request #2407 from splunk/trangl-o11ydocs-6536-update-snow-requirements
Add SNOW Events role requirements
2 parents 89f24d9 + 28b5e74 commit e2a9561

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

admin/notif-services/servicenow.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ Before you set up the integration, choose a ServiceNow issue type from the follo
4444
- ``user_admin``, ``itil``
4545
- ``/api/now/v2/table/incident``
4646
* - Event
47-
- None
47+
- ``evt_mgmt_integration``, only if :guilabel:`Requires ACL authorization` is selected for :strong:`Inbound Event Default Bulk Endpoint` in :strong:`Scripted Rest APIs`. To learn more, see the :new-page:`ServiceNow support article on events <https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0993277>`.
4848
- ``/api/global/em/jsonv2``
4949

5050
Make note of the role and receiving endpoint that corresponds to your issue type before proceeding with :ref:`servicenow2`.
@@ -112,9 +112,9 @@ To create a ServiceNow integration in Splunk Observability Cloud:
112112

113113
To troubleshoot potential blind server-side request forgeries (SSRF), Splunk Observability Cloud has included ``\*.service-now.com`` on an allow list. As a result, if you enter a domain name that is rejected by Splunk Observability Cloud, contact :ref:`support` to update the allow list of domain names.
114114

115-
#. Select :strong:`Incident`, :strong:`Problem`, or :strong:`Event` to indicate the issue type you want the integration to create in ServiceNow. If necessary, you can create a second integration using the other issue type. This lets you create an incident issue for one detector rule and a problem issue for another detector rule. The following table shows the roles required to create each issue type:
115+
#. Select :strong:`Incident`, :strong:`Problem`, or :strong:`Event` to indicate the issue type you want the integration to create in ServiceNow. If necessary, you can create a second integration using another issue type. This lets you create an incident issue for one detector rule and a problem issue for another detector rule.
116116

117-
#. :strong:`Save`.
117+
#. Select :strong:`Save`.
118118

119119
#. If Splunk Observability Cloud can validate the ServiceNow username, password, and instance name combination, a :strong:`Validated!` success message displays. If an error displays instead, make sure that the values you entered match the values in ServiceNow.
120120

0 commit comments

Comments
 (0)