Ardoq’s ServiceNow integration is a two-way integration that allows you to:
Import your ServiceNow data as components and references in Ardoq so you can visualize the dependencies that exist between them and other components in your architecture such as applications, departments, people, etc.
Export your modified ServiceNow data from Ardoq to ServiceNow to to maintain your data up to date at all times.
In this article, we’ll cover how to export your Ardoq data to ServiceNow. To learn how to import your ServiceNow data to Ardoq, refer to this KB article.
Table of Contents:
Before Getting Started
Know that:
New components and references created in Ardoq will be exported to ServiceNow.
Existing components and references that are not modified will not be exported to ServiceNow.
You need to have an existing ServiceNow connection. If you have none, set up your ServiceNow account first. Next, create a new connection by navigating to “Home > Import & Integrations > ServiceNow” and fill in the following details:
Name: The name of this ServiceNow connection, so it can be identified in the list
Base URL: The URL to your ServiceNow instance
Username and Password: Your ServiceNow username and password
How To Export Your Data From Ardoq To ServiceNow
This guide shows you how to import your server data from ServiceNow to Ardoq. We'll cover the process step-by-step.
To export your data, first do the same steps as in the import flow how-to guide and then come back here. Once you reach the “Configure” step where you map your data to Ardoq’s column types (step 8), you will be able to export your data.
1. Navigate to “Home > Import & Integrations” and select ServiceNow.
2. When in the ServiceNow integration, navigate to the top right corner and click 'Create new export'.
Please note: To run an export from Ardoq to ServiceNow, you need to have admin permissions.
3. During Step 1 of the export process, you can choose to either export data using a saved configuration or manually select a connection, along with the specific tables and fields you want to export to ServiceNow.
3. Search for the cmdb_ci_server and any other server table(s). Please note that the list is filtered based on the provided user's access rights. Depending on your user's roles, that might take some time.
4. Select the name of the table from the menu. Then select the fields you want to export. You also have the option to run a Query for specific items.
You can use the “Search” input to filter the list of fields.
Select each field you want to fetch or click the “Select All” button to select all fields.
Reference fields will show two entries in the field list: the label of the reference, and the ServiceNow sys-id of the referenced record. This allows you to create references based on either the ID or name.
Once you have chosen all tables and fields, click the "Configure Data" button in the bottom right corner to move to the next step.
6. Once you have selected the tables and which field, click 'Configure Data' in the bottom right corner. Following this, choose which Servers to configure and the target workspace.
7. Next, configure the columns so that the values match your workspace metamodel structure. Here, you can also define the references you wish to export by selecting “Reference” in a column configuration. See the “How to create references with your ServiceNow data” HC article for a step-by-step guide on how to create references for ServiceNow data.
8. Click on the ‘Review Export' button to perform a test run and get a summary of what would change in ServiceNow.
9. Click on ‘Export my data’ to apply the changes in your ServiceNow instance. Make sure to map the "Sys Id" column as a "Custom Id" during column mapping. This way, the exporter is able to match Ardoq elements with ServiceNow elements.
10. In the final part of the export, you can choose to set up daily or weekly exports to ServiceNow of the data you have chosen. Now your data has been exported to ServiceNow - to navigate to ServiceNow, you can click the 'Open ServiceNow' button in the bottom right corner.
FAQ: Exporting Specific Component Types from Ardoq to ServiceNow
When Exporting data from Ardoq into ServiceNow, it's common to encounter a scenario where a single Ardoq workspace contains multiple component types. By default, all component data within this workspace might get transferred to ServiceNow tables. To refine this process and export only specific component types, follow the steps below:
1. Set Up a Calculated URL Field in Ardoq: Implement a calculated URL field. Utilize the following query, ensuring it's applied exclusively to the component type intended for export to ServiceNow
g.V(ids).
project('id', 'name', 'value').
by(id).
by('name').
by(label)
2. In the ServiceNow table, Either create a new column of type 'string' or identify an existing column within the ServiceNow table designated for this data integration. Please ensure that this selected column contains only dummy data. Ex: Short Description.
3. Connect the previously specified ServiceNow column to the Ardoq field(Calculated field Application URL Export). In the export configuration step, apply a filter with a condition to check if the column data "Is not Empty".
To do this, click 'Advanced', followed by 'Add advanced configuration' and 'Filter data'.
4. . Execute the Export. Once you've initiated the export process, Ardoq will selectively transfer data based only on the specified component types. By following these steps, you can ensure a targeted and efficient data integration from Ardoq to ServiceNow.
Note: In order for this work around to function as intended, it's essential that both fields are present in both Ardoq and ServiceNow. The filter will exclusively be applied to Ardoq components if the field exists in both systems. In such cases, we recommend using the 'class' column as the ServiceNow field, which consistently exists and aligns with the same concept as the Ardoq type.
Please refer to ServiceNow Integration Permissions Overview for setting up permissions for Service now Export.
FAQ
What should I know when exporting data to ServiceNow, especially regarding the sys_id?
When exporting data to ServiceNow, avoid pushing data to different environments to prevent issues with sys_id updates. Syncing multiple environments in the same workspace is not recommended due to potential integration issues, which can lead to duplicate entries in ServiceNow.
Troubleshooting The Export
If your ServiceNow data remains unchanged after a successful export in Ardoq, double check your user has write access on the ServiceNow tables in question.
If the issue persists, please contact us at support@ardoq.com or via the in-app chat.