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 keep your data up to date at all times.
Before Getting Started
You will need to have an existing ServiceNow connection configured in Ardoq. Read our article on Importing Data into Ardoq from ServiceNow for details on getting a connection set up.
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.
Note: The ServiceNow Export integration requires that the sys_choice table be accessible to the integration user account.
How To Export Your Data From Ardoq To ServiceNow
To export your data, you'll need to have data in Ardoq first. You can read about importing ServiceNow data into Ardoq in our import flow how-to guide.
This guide shows you how to import your server data from ServiceNow to Ardoq. We'll cover the process step-by-step.
From the main menu, navigate to Home > Import and Integrations, and select ServiceNow.
On the next page, select Create new export from the top right corner.
Note: To run an export from Ardoq to ServiceNow, you need to have admin permissions.
Select your configured connection.
Select the tables and fields in ServiceNow that will be affected by your export, and continue to the Configure data step.
You will need to three things for the export to work:
A component name
A Custom ID that maps to the Sys ID in ServiceNow and points to an existing Sys ID in the selected workspace
This step is necessary to match Ardoq elements to ServiceNow elements
Any additional fields you want to export
Note: 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.
Proceed to Review and Export steps when ready.
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 > Add advanced configuration > 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.
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.