ServiceNow Exporter Feature Deprecated
The ServiceNow Exporter feature is now deprecated and will be removed from Ardoq later this year. While we will continue to support some existing users for a period, we are no longer recommending its use.
As part of our ongoing efforts to improve our platform and services, we have made the decision to deprecate the ServiceNow Exporter feature in Ardoq. This means that the feature will no longer be available for use and will be removed from the platform in the near future.
We understand that this may cause inconvenience for some of our users, and we apologize for any disruption this may cause. However, we believe that this decision will ultimately benefit our users by allowing us to focus on providing the best possible experience with our core features.
What does this mean for existing users?
If you are currently using the ServiceNow Exporter feature, please note that we will continue to support it for a period of time. However, we strongly recommend that you start transitioning to alternative methods of exporting your data from Ardoq.
If you have any questions or concerns about this transition, please don't hesitate to reach out to our support team. We are here to help and will do our best to assist you with the transition process.
Why are we deprecating this feature?
As mentioned earlier, our goal is to provide the best possible experience for our users. After careful consideration, we have determined that the ServiceNow Exporter feature is no longer meeting our standards and is not aligned with our long-term vision for the platform.
We are constantly evaluating and improving our features and services, and we believe that this decision will allow us to focus on providing the best possible experience for our users.
What are the alternatives?
While we understand that the ServiceNow Exporter feature may have been a convenient way for some users to export their data, there are alternative methods available that can achieve the same result.
One option is to use our API to export your data programmatically. This allows for more flexibility and customization in the export process.
Another option is to use our built-in export feature, which allows you to export your data in various formats such as CSV or Excel.
If you need assistance with setting up these alternatives, please don't hesitate to reach out to our support team.
Conclusion
In conclusion, we want to thank all of our users who have used the ServiceNow Exporter feature in the past. We hope that you understand our decision and we apologize for any inconvenience this may cause.
As always, we are committed to providing the best possible experience for our users and we will continue to work towards improving our platform and services.
Thank you for your understanding and continued support.
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.
To export data from Ardoq to ServiceNow, you need to have previously done an import from ServiceNow and have a saved configuration. The configuration will preserve the mapping between between ServiceNow tables and Ardoq tables — an export is not advised without a saved configuration.
Exporting from Ardoq to ServiceNow requires thinking a little differently than the importing process.
Step 1 — Select destination tables in ServiceNow
Your configuration will pre-select the relevant tables for you. These will be the same tables that you imported data from.
While this looks exactly like selecting source tables during a ServiceNow import, you are actually selecting the tables that will serve as the destination for your Ardoq data.
Proceed to the Configuration step when you've selected the tables you want to export Ardoq data into.
Step 2 — Configure tables for receiving Ardoq data
For the selection Table rows contain you will need to select Components.
Next, you will need to select the source workspace that holds the data you want to export. This will likely be the workspace you used to import your ServiceNow data.
Keep in mind that the tabular data presented to you does not show the data in the workspace you have selected. Instead, it shows the data currently in the destination ServiceNow table. You will need to open a separate window and look at your selected workspace to see how it maps back to the ServiceNow table. As long as the data in your workspace was originally imported from ServiceNow, it should follow the same table structure as the ServiceNow table being previewed.
At a minimum, you will need to map two fields in the table to ensure that the data in Ardoq matches the ServiceNow structure:
A component name
This should be clear from your existing workspace component names.
The Sys ID field mapped as a Custom ID
This is the field that will be used as the unique identifier to match Ardoq components to ServiceNow entries.
Without it, you cannot export Ardoq data to ServiceNow.
Additionally, you can also map any additional fields you want to export to ServiceNow.
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.
Finally, 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.