Skip to main content

Setting up ServiceNow Connection

This is an optional task that needs to be done only If you plan to use ServiceNow to process the approved content changes for source of record fields. You must set up the connection to your ServiceNow instance before configuring the automation.

How the integration with ServiceNow works?

  • Processes performed in ServiceNow: When a change suggested to a Source of record filed is approved in data.world, a corresponding ticket is automatically created in ServiceNow. In most cases, a user who has edit access to the resource will take that ticket, make changes to the Source of record filed , and then close the ticket.

  •  Data transferred from data.world to ServiceNow: The integration transfers essential information related to the suggested change from data.world to ServiceNow. This typically includes details such as the suggester’s identity and a link to the specific resource in data.world for which the change is suggested. This data is stored in ServiceNow’s tables designated for handling such requests, often within the Incident or Service Request tables, depending on your organization’s configuration. 

  • Frequency of data transfer: The ticket creation from data.world to ServiceNow occurs in real-time. As soon as a content change is approved in data.world, the integration triggers the creation of a corresponding ticket in ServiceNow without delay.

Creating an OAuth application endpoint in ServiceNow

To create an OAuth application endpoint in ServiceNow:

  1. In your ServiceNow instance, browse to All > System OAuth > Application Registry.

  2. On the Application Registries page, Click New.

  3. On the What kind of OAuth application? page click Create an OAuth API endpoint for external clients.

  4. On the Application Registries - New Record page, in the Name field provide a unique name for your configuration. Click Submit.

  5. Note down the Client ID and Client Secret information. You will use this information while configuring the connection in data.world.

Configuring the connection in data.world

To set up the connection:

  1. On the Organization profile page, go to the Settings tab.

  2. In the Connection manager section, click the Add connection button.

  3. In the Add an organization-level connection window, select ServiceNow.

  4. In the Add a new ServiceNow connection window, set the following:

    • Display name: Provide a name for the connection.

    • Server: Provide the ServiceNow URL. For example, 8Bank.service-now.com

    • Connection username: Provide the ServiceNow username for the connection. This should be the account you want recorded as the creator of tickets in ServiceNow.

    • Connection password: Provide the password for the username you are using to connect to your ServiceNow instance.

    • Client ID: Provide the client ID for your account you noted from ServiceNow.

    • Client Secret: Provide the client secret you noted from ServiceNow.

  5. Once done, click the Configure button.

Configuring a custom table in ServiceNow

This section walks you through the process of creating a custom table for storing the tickets that are automatically created when a suggested change for a Source of record metadata field is triggered. After a suggested change is approved in data.world, a corresponding record will automatically appear in ServiceNow in the custom table, allowing your teams to take action within their existing workflow.

Get the XML file from data.world support team

Import the ServiceNow_UpdateSet_dataworld_Suggest_Changes.xml file in ServiceNow

To ensure the required custom table is created properly, you will need to import and commit our prebuilt Update Set.

To import the ServiceNow_UpdateSet_dataworld_Suggest_Changes.xml file in ServiceNow:

  1. In your ServiceNow instance, navigate to: System Update Sets > Retrieved Update Sets.

  2. Click on Import Update Set from XML.

  3. Upload the ServiceNow_UpdateSet_dataworld_Suggest_Changes.xml file provided by data.world.

  4. After uploading, you will see a new entry in the list. Click to open the new Update Set.

  5. Review the details and then click Commit Update Set.

Important

Ensure you commit the update set in your development or staging instance first, and thoroughly test before moving to production.

Locate the custom table added for recording suggested changes

After committing the update set, a new custom table named something like u_data_world_change_requests will be created. This table is where all Suggestion Change records will be logged.

To locate the custom table:

  1. Navigate to: System Definition > Tables

  2. Search for the table name, for example, u_data_world_change_requests. This table is where all Suggestion Change records will be logged.

In this section: