Skip to content

Commit f691662

Browse files
committed
[DOCS] Fix casing in servicenow docs config (#115634)
(cherry picked from commit f1de84b)
1 parent b142f88 commit f691662

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

docs/reference/connector/docs/connectors-servicenow.asciidoc

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -81,15 +81,15 @@ Comma-separated list of services to fetch data from ServiceNow. If the value is
8181
- link:https://docs.servicenow.com/bundle/tokyo-it-service-management/page/product/incident-management/concept/c_IncidentManagement.html[Incident]
8282
- link:https://docs.servicenow.com/bundle/tokyo-servicenow-platform/page/use/service-catalog-requests/task/t_AddNewRequestItems.html[Requested Item]
8383
- link:https://docs.servicenow.com/bundle/tokyo-customer-service-management/page/product/customer-service-management/task/t_SearchTheKnowledgeBase.html[Knowledge]
84-
- link:https://docs.servicenow.com/bundle/tokyo-it-service-management/page/product/change-management/task/t_CreateAChange.html[Change Request]
84+
- link:https://docs.servicenow.com/bundle/tokyo-it-service-management/page/product/change-management/task/t_CreateAChange.html[Change request]
8585
+
8686
[NOTE]
8787
====
8888
If you have configured a custom service, the `*` value will not fetch data from the basic services above by default. In this case you'll need to mention these service names explicitly.
8989
====
9090
Default value is `*`. Examples:
9191
+
92-
- `User, Incident, Requested Item, Knowledge, Change Request`
92+
- `User, Incident, Requested Item, Knowledge, Change request`
9393
- `*`
9494
9595
Enable document level security::
@@ -139,7 +139,7 @@ For default services, connectors use the following roles to find users who have
139139
140140
| Knowledge | `admin`, `knowledge`, `knowledge_manager`, `knowledge_admin`
141141
142-
| Change Request | `admin`, `sn_change_read`, `itil`
142+
| Change request | `admin`, `sn_change_read`, `itil`
143143
|===
144144
145145
For services other than these defaults, the connector iterates over access controls with `read` operations and finds the respective roles for those services.
@@ -305,15 +305,15 @@ Comma-separated list of services to fetch data from ServiceNow. If the value is
305305
- link:https://docs.servicenow.com/bundle/tokyo-it-service-management/page/product/incident-management/concept/c_IncidentManagement.html[Incident]
306306
- link:https://docs.servicenow.com/bundle/tokyo-servicenow-platform/page/use/service-catalog-requests/task/t_AddNewRequestItems.html[Requested Item]
307307
- link:https://docs.servicenow.com/bundle/tokyo-customer-service-management/page/product/customer-service-management/task/t_SearchTheKnowledgeBase.html[Knowledge]
308-
- link:https://docs.servicenow.com/bundle/tokyo-it-service-management/page/product/change-management/task/t_CreateAChange.html[Change Request]
308+
- link:https://docs.servicenow.com/bundle/tokyo-it-service-management/page/product/change-management/task/t_CreateAChange.html[Change request]
309309
+
310310
[NOTE]
311311
====
312312
If you have configured a custom service, the `*` value will not fetch data from the basic services above by default. In this case you'll need to mention these service names explicitly.
313313
====
314314
Default value is `*`. Examples:
315315
+
316-
- `User, Incident, Requested Item, Knowledge, Change Request`
316+
- `User, Incident, Requested Item, Knowledge, Change request`
317317
- `*`
318318
319319
`retry_count`::
@@ -374,7 +374,7 @@ For default services, connectors use the following roles to find users who have
374374
375375
| Knowledge | `admin`, `knowledge`, `knowledge_manager`, `knowledge_admin`
376376
377-
| Change Request | `admin`, `sn_change_read`, `itil`
377+
| Change request | `admin`, `sn_change_read`, `itil`
378378
|===
379379
380380
For services other than these defaults, the connector iterates over access controls with `read` operations and finds the respective roles for those services.

0 commit comments

Comments
 (0)