- Step 1 - Installing Coveo for ServiceNow
- Step 2 - Creating a ServiceNow Source
- Step 3 - Replacing the Service Portal Search Page
- Step 4 - Replacing the Service Portal Search Boxes
- Step 5 - Configuring the Case Deflection Panel
- Step 6 - Configuring the Insight Panel
- Step 7 - Configuring a Recommendations Panel
- Step 8 - Configuring Query Filters
- Step 9 - Configuring Machine Learning Models
Creating a ServiceNow Source
This source can be shared or private (see Content Security). By default, your ServiceNow source starts a rescan every day to retrieve ServiceNow content changes, i.e., item additions, modifications, and deletions (see Edit a Source Schedule).
Create a Crawling Account
This account must be an administrator account that has access to the ServiceNow content you want to make searchable.
Add or Edit a ServiceNow Source
When you have the required privileges, you can create a ServiceNow source to make your instance content searchable.
- Ensure that Coveo for ServiceNow is installed in your ServiceNow instance and connected to a Coveo Cloud organization (see Installing Coveo for ServiceNow).
In the Coveo Cloud administration console for this organization, go to the Add/Edit a ServiceNow Source panel:
To add a source, in the main menu, under Content, select Sources > Add source button > ServiceNow.
To edit a source, in the main menu, under Content, select Sources > source row > Edit in the Action bar.
In the Add/Edit a ServiceNow Source panel, in the Configuration tab, enter appropriate parameter values:
A descriptive name for your source under 255 characters (not already in use for another source in this organization).
You cannot change the source name once it is created.
Your instance name. Typically, a ServiceNow instance URL includes the instance name.
Your instance URL is
https://myinstance.service-now.com, so your instance name is
Character optical recognition (OCR)
Check this box if you want Coveo Cloud to extract text from image files and/or PDF files containing images (see Enable Optical Character Recognition). OCR-extracted text is processed as item data, meaning that it is fully searchable and will appear in the item Quick View (see Search Result Quick View).
When adding a source, if you have more than one logical (non-Elasticsearch) index in your organization, select the index in which the retrieved content will be stored (see Leverage Multiple Coveo Indexes). If your organization only has one index, this drop-down menu is not visible and you have no decision to make.
Select who can search the ServiceNow content (see Content Security). Your options are:
Shared - Everyone
Private - Only you, the source creator
In the Authentication section, select an authentication option:
If you select Basic authentication, enter the Username and Password of a dedicated ServiceNow account that has access to the content you want to make searchable.
If you select OAuth 2.0, which is the most secure and therefore recommended option:
- Click Authorize Account.
- In the Sign in to ServiceNow window that appears, enter your ServiceNow Instance name, Client ID, and Client secret, and then click Authorize. Your client ID and client secret can be found in the Coveo application registry:
- In the Now Platform UI of your ServiceNow instance, navigate to System OAuth > Application Registry.
- In the Applications Registries list, click the Coveo registry.
- In the ServiceNow window that appears, enter the User name and Password of a ServiceNow administrator account that has access to the desired content, and then click Login (see Create a Crawling Account).
- Under [Application registry name] would like to connect to your ServiceNow account on instance [instance name], click Allow.
Once you have authorized your account, the OAuth 2.0 handshake must be refreshed once in a while. The default lifespan of a token is 2 years, but ServiceNow allows you to change this duration.
In the Content to Include section, the JSON configuration shows your source configuration. If you want to edit it, see Generic REST API Source Reference and Generic REST API Source Tutorial, as the Generic REST API source and the ServiceNow source require a similar JSON configuration. Incidentally, the Generic REST API Source JSON Configuration Examples include a basic ServiceNow source configuration.
- In the Access tab, determine whether each group and API key can view or edit the source configuration (see Understanding Resource Access):
- In the Access Level column, select View or Edit for each available group.
- On the left-hand side of the tab, if available, click Groups or API Keys to switch lists.
If you remove the Edit access level from all the groups of which you are a member, you will not be able to edit the source again after saving. Only administrators and members of other groups that have Edit access on this resource will be able to do so. To keep your ability to edit this resource, you must grant the Edit access level to at least one of your groups.
Complete your source addition or edition:
Click Add Source/Save if you edited your source JSON configuration or if you want to save your source changes without starting a build/rebuild, for instance when planning to make other changes soon.
In the Sources page, you need to click Start initial build or Start initial rebuild in the source Status column to respectively add the source content and make your changes effective.
Click Add and Build Source/Save and Rebuild Source if you did not edit your source JSON configuration, are done editing the source, and want to make changes effective.
Once the source is built or rebuilt, you can review its content in the content browser (see Inspect Items With the Content Browser).
If you edited your source JSON configuration, you may have decided to populate fields that are not Coveo Cloud default fields (see Understanding Fields). If you have not already created these fields for another source, you must create them in the Fields page before building your source (see Add or Edit Fields and Field Origins).
You decided to retrieve picture URIs and to have Coveo Cloud populate the
otheraddressfield with this data. Your item metadata therefore contains:
However, since the
otheraddressfield is not a default field like
date, you must create it.
You have another ServiceNow source populating the custom field
otheraddress. When creating your new source, you therefore do not need to create this field, as it is already in the Fields page.
Ensure that your source maps correctly all the fields to populate (see Manage Source Mappings). If a field does not have a mapping, you must create one.
You map the
otheraddressfield with the following rule:
In the Sources page, in the source Status column, click Start initial build or Start required rebuild to respectively start retrieving the source content or make your changes effective.
Once the source is built or rebuilt, you can review its content in the content browser (see Content Browser - Page).
- Optionally, you can create additional sources in your Coveo Cloud organization (see Available Coveo Cloud V2 Connectors).
- To begin leveraging the content of your Coveo Cloud organization index in ServiceNow, you should replace your current Service Portal search page with a Coveo search page (see Replacing the Service Portal Search Page).