Conversation with Merlin [email protected] · Mon Dec 04 2023

how to use service now rest api in code for authentication, ticket raising, and gettting status back

To use the ServiceNow REST API in code for authentication, ticket raising, and getting status back, you would typically follow these steps:

  1. Authentication: Before you can interact with the ServiceNow API, you need authenticate. This generally involves providing a username and password, and possibly other security credentials.

    const sn = require('servicenow-rest-api'); const ServiceNow = sn('INSTANCE', 'USERID', 'PASSWORD'); ServiceNow.Authenticate().then(function(response){ console.log(response.status); // Authentication status });

Replace 'INSTANCE', 'USERID', and 'PASSWORD' with your ServiceNow instance name and your credentials.

  1. Raising a Ticket (Creating an Incident): Once authenticated, you can create a ticket (incident) by making a POST to the table API.

    // Define the data for the new incident const incidentData = { short_description: 'Short description of the issue', urgency: '1', // 1 - High, 2 - Medium, 3 - Low : '1', // 1 - High, 2 - Medium, 3 - Low description: 'Full description of the issue', // ... You can other fields as required }; // Function to create a new incident ServiceNow.createNewTask('incident', incidentData, function(result){ console.log(result); // Log the response which includes details of the created incident });
  2. Getting the Status of a Ticket: To get the of a ticket, you can make a GET request, either to list all tickets or to retrieve a specific ticket by its sys_id.

    For a specific ticket:

    const sysId = 'YOUR_TICKET_SYS_ID'; // Replace with your ticket's sys_id // Function to get the data a specific incident using sys_id ServiceNow.getTableData('incident', sysId, function(result){ console.log(result); // Log the status of the incident });

`

To retrieve all incidents:

Function to get data from the 'incident' table ServiceNow.getTableData('incident', '',(result){ console.log(result); // Log all the incidents });

Notes:

  • This code uses a Node.js wrapper library for the ServiceNow REST API. Make sure you have this library installed via npm:
    npm install servicenow-rest-api
  • The actual field values and the of the incident data will depend on your ServiceNow configuration.
  • This code is asynchronous, so you may need to use promises or async/await to handle the responses properly in a real-world application.
  • The getTableData method generally requires additional parameters to filter and specify the result set you to retrieve; make sure you consult the ServiceNow API documentation for details on the query parameters you can use.

ServiceNow REST API\n\nNode.JS wrapper library for ServiceNow REST API.\n\nMissing a feature? Raise a github issue here\nUpdates\nv1.2.2\n\nNew method to fetch change tasks\nBumped axios version\n\nTable of Contents\n\nInstalling\nBasic Usage\n\nRequest\nResponse\n\n\nSupported REST API calls\nFunctions\n\n1. ServiceNow.Authenticate\n\nRequest\nResponse\n\n\n2. ServiceNow.getSampleData\n\nRequest\nResponse\n\n\n3. ServiceNow.getTableData\n\nRequest\nResponse\n\n\n4. ServiceNow.getSysId\n\nRequest\nResponse\n\n\n5. ServiceNow.createNewTask\n\nRequest\nResponse\n\n\n6. ServiceNow.UpdateTask\n\nRequest\nResponse\n\n\n7. ServiceNow.DeleteTask\n\nRequest\nResponse\n\n\n8. ServiceNow.setNetworkOptions\n\nRequest\n\n\n9. ServiceNow.getAttachmentMetaData\n\nRequest\nResponse\n\n\n10. ServiceNow.getAttachment\n\nRequest\nResponse\n\n\n11. ServiceNow.getAllAttachmentsMetaData\n\nRequest\nResponse\n\n\n12. ServiceNow.getChangeTasks\n\nRequest\nResponse\n\n\n\n\nExamples\n\n1. Get critical incidents which are open for last 6 months.\n\nRequest\nResponse\n\n\n2. Create an Emergency change to reboot server\n\nRequest\nResponse\n\n\n3. Elevate priority of ticket\n\nRequest\nResponse\n\n\n4. Set Custom Proxy\n\nRequest\n\n\n5. Downlaod Attachment\n\nRequest\nResponse\n\n\n\n\nLicense\nVersion\n\nInstalling\nRun npm install servicenow-rest-api to install the package.\nBasic Usage\nRequest\n\nGet reference to servicenow package.\nInitialize servicenow object.\nCall authenticate function.\nYou can now access Servicenow data by calling functions.\n\nconst sn=require('servicenow-rest-api');\n\nconst ServiceNow=new sn('_INSTANCE','_USERID','_PASSWORD');\n\nServiceNow.Authenticate();\n\nServiceNow.getSampleData('change_request',(res)=>{ // \n console.log(res);\n});\n\nProxy Settings\nconst sn=require('servicenow-rest-api');\n\nconst ServiceNow=new sn('_INSTANCE','_USERID','_PASSWORD');\n\nconst HttpsProxyAgent = require('https-proxy-agent');\n\n// Your Proxy details\nlet agent = new HttpsProxyAgent({host: \"123.252.137.238\", port: \"54107\"});\n\n// Call this method before Authenticate\nServiceNow.setNetworkOptions({\n httpsAgent: agent\n})\n\nServiceNow.Authenticate();\n\nServiceNow.getSampleData('change_request',(res)=>{ // \n console.log(res);\n});\n\nResponse\n[ { parent: '',\n reason: '',\n made_sla: 'false',\n backout_plan: 'Current prod environment to be snapshotted with VmWare\\n prior to change.\\n ',\n watch_list: '',\n upon_reject: '',\n sys_updated_on: '2017-08-10 12:42:23',\n type: 'normal',\n conflict_status: '',\n approval_history: '',\n number: 'CHG0000001',\n test_plan: 'Multi-User testing on Sunday night',\n cab_delegate: '',\n sys_updated_by: 'admin',\n .\n .\n .\n\nSupported REST API calls\nIn this package, wrappers are available for below REST interfaces.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nAPIGETPOSTPUTDELETETable API/now/v2/table/{tableName}now/v2/table/{tableName}now/v2/table/{tableName}/{sys_id}now/v2/table/{tableName}/{sys_id}/now/v2/table/{tableName}/{sys_id}Attachment API/now/attachment/{sys_id}/now/attachment/{sys_id}/file\nFunctions\n1. ServiceNow.Authenticate\nIf you need to set custom network options, call this method before Authenticate.\n\n\n\n\n\n\n\n\n\n\n\nParametersCallback function\nRequest\nServiceNow.Authenticate(res=>{\n console.log(res.status);\n});\n\nResponse\nres.status\n\nFor complete response use res.raw\n{ status: 200,\n statusText: 'OK',\n headers:\n { 'set-cookie':\n [_cookieinfo],\n 'x-is-logged-in': 'true',\n 'x-total-count': '1',\n pragma: 'no-store,no-cache',\n 'cache-control': 'no-cache,no-store,must-revalidate,max-age=-1',\n expires: '0',\n 'content-type': 'application/json;charset=UTF-8',\n 'transfer-encoding': 'chunked',\n .\n .\n .\n\n\n2. ServiceNow.getSampleData\nThis function can be used as a reference to get sample data for tables in ServiceNow. This can be used to check the fields in a table.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nParametersDes

github.com

Integrating with ServiceNow Overview Logging trouble tickets Configuring ServiceNow in Applications Manager Prerequisites Steps to configure Configuring Event Preferences Ticket Settings Reopen Settings Update Settings Accessing from Applications Manager Configuration Item Details in CMDB APIs used in APM for incident management in ServiceNow Overview ServiceNow is a web-based Help Desk and Asset Management software. With ServiceNow, you can automatically log trouble tickets for specific alarms and manage incidents from Applications Manager. Logging trouble tickets Applications Manager has the ability to automatically log trouble tickets for specific alarms and to notify the concerned technician when a particular process exceeds the set threshold point. Along with the provision to send emails, SMS messages, and other notifications, alarms can also be tracked by automatically logging trouble tickets in a help desk software. Applications Manager takes care of two-way synchronization of Alerts and Ticket statuses with ServiceNow. For example, you can automatically log a ticket when an alarm is raised, reopen the ticket whenever an alarm reoccurs, or close the ticket if the alarm is cleared. Additionally, the alerts under the Alarms tab include a Ticket Icon that loads the ticket raised when clicked on. Configuring ServiceNow in Applications Manager This section describes the method in which ServiceNow the settings are to be configured in Applications Manager: Prerequisites The ServiceNow user should have the following roles required for the corresponding options for successful integration in Applications Manager: Incident management : itil, itil_admin and personalize_choices CI Sync : itil, itil_admin, personalize_choices and personalize_dictionary Event sync : evt_mgmt_integration Log in to ServiceNow as an admin user and perform the following steps: Go to System Definition and then Tables. Search for "Incident". Click on the entry that has the Label as "Incident". This will load the Incident table. Now, select Controls tab. Enable "Create access controls" and type itil_admin in the "User role" field. Save this table. Steps to configure Under Settingstab, click onAdd-On SettingsunderProduct Settings. An Add-on Settings table is displayed. Click onAddaction for HelpDesk. This takes you to the ManageEngine ServiceDesk Plus Server Details page with a choice to Select HelpDesk Product. Choose ServiceNow. Provide theInstance name (e.g.: [instancename].service-now.com),Username andPassword. Secure connection will be used by default while connecting to ServiceNow and so the protocol must not be specified in the Instance field. Enable the Mail Notification for Connectivity Failure toggle button if you wish to trigger mail notifications in case of connectivity failures. After enabling this option, enter the following details: Configure the email to which the notification has to be sent. You can configure either by choosing Admin email (Mail address configured for the admin user or the mail address in SMTP configuration) or by selecting email actions to be triggered for the selected email from the dropdown. Enable the Append Custom Message checkbox if you want to append customized text messages along with the mail notifcation. Enable the Repeat mails until successful connection checkbox to repeat mail notifications until connection is established successfully. After enabling, specify the Repeat Interval (in minutes) after which mail notification has to be repeated. Enable the Add Events toggle button to configure events. Enabling this option will automatically disable Log Tickets. Either Events or Ticketing can be enabled at a time. By enabling Log tickets toggle button you have the option to configure Ticket Settings. Enable Configuration Item (CI) sync toggle button to configure Configuration Item Settings. Test if the connection is working and save the settings. Configuring Event Preferences For ServiceNow integration, Add Events opti

manageengine.com

Configuration Flow to Connect Ticket Systems with SAP Cloud ALM Establish Connectivity from SAP Cloud ALM to the external ticket system Case 1: The external ticket system is notServiceNowIncident Management To connect from SAP Cloud ALM to the external ticket system, a destination must be configured in the BTP subaccount, where SAP Cloud ALM is deployed. Log on to BTP Cockpit and enter your SAP Cloud ALM subaccount Navigate to "Connectivity" > "Destinations" Click "New Destination" Name: Enter a destination name that identifies the API endpoint of your ticket system or the API middleware provider Type: HTTP Description: A description of the destination URL: URL of the API endpoint of your ticket system or the used API middleware Proxy Type: Internet Authentication: use the authentication method of the target API. Authentication method NoAuthentication is not supported by SAP Cloud ALM integrations Enter the required authentication information depending on the authentication method Click the "Save" button Case 2:The external ticket system isServiceNowIncident Management To establish connectivity toServiceNowIncident Management you can ignore the steps above and configure the connectivity in Landscape Management in SAP Cloud ALM. Refer to "Example: Configure Integration with ServiceNow Incident Management" below for details. Create Mapping To map and convert the available values of the event situation outbound integration with the API definition of the target system a field or value mapping is necessary in most cases. This mapping can be achieved for simple integrations by providing a mapping file in SAP Cloud ALM directly. The possible options for mappings are described in the SAP Cloud ALM documentation. The format of the event situation API is also documented there. The return values of the integration must return an externalId and externalNumber of the created ticket. During runtime these values are stored in SAP Cloud ALM to map the event situation in SAP Cloud ALM to the ticket in the ticket system. If the provided mapping capabilities are not sufficient or if a single API call a single API call from SAP Cloud ALM to the ticket system is not sufficient to create or update a ticket, additional integration logic must be defined in an integration system. Maintain External API With the destination and the mapping file the definition of the external API endpoint in Cloud ALM can be completed by creating a webhook and the subscription. To make the integration available as for creation of tickets, the External Ressource Type must be Incident. As Destination Type the name of the ticket system can be used (free text field). The Ressource Type in the subscription definition must be set to CALM Event Situation. Configure External API as Event Action After the subscription is fully maintained as explained above the available subscriptions of type incident are then available in the event configuration for Create Ticket event action. To enable ticket creation the switch create ticket needs to be turned on and the subscription with the mapping and webhook for this event type can be selected. You can configure the event actions for monitoring events from the configuration page in the relevant monitoring application (Business Process Monitoring, Integration & Exception Monitoring, Job & Automation Monitoring, Health Monitoring). You can configure theevent actions for status events (Disruptions, Degradations , Maintenance, Customer Communication events from Business Service Management or SAP for Me Notifications) as described here. Setup Event Situation Confirmation if Ticket is Solved For monitoring events it is required to update the status of event situations whenever a ticket is solved. Doing so will ensure, that the corresponding event situation for the ticket is also completed in Cloud ALM and new occurrences of the same issue will no longer try to update the already solved ticket, but creates a new ticket instead. To achieve this th

support.sap.com

provide this code in python

Here is an example of how you might use Python to work with the ServiceNow REST API for the tasks of authentication, ticket raising (creating an incident), and getting the status of the ticket. This example uses the requests library for HTTP requests, which you need to install using pip install requests if you haven't already.

Please replace your_instance, your_username, and your_password with your actual ServiceNow instance and credentials.

requests from requests.auth import HTTPBasicAuth # Replace these variables with your ServiceNow instance and credentials instance = 'your_instance' user = 'your_username' pwd = 'your_password' # Set the request parameters url = f'https://{instance}.service-now.com/api/now/table/incident' # Set proper headers headers = { "Content-Type": "application/json", "Accept": "application/json" } # Do the HTTP request for authentication response = requests.get(url, auth=HTTPBasicAuth(user, pwd), headers=headers) # Check for HTTP codes other than 200 if response.status_code != 200: print('Status:', response.status_code, 'Headers:', response.headers, 'Error Response:', response.json()) exit() # Decode the JSON response into a dictionary and use the data data = response.json() print(data) # Example payload for a new ticket new_incident_data = { "short_description": "This is a test incident", "category": "software", } # Making a POST request to create a new incident response = requests.post(url, auth=HTTPBasicAuth(user, pwd), headers=headers, json=new_incident_data) if response.status_code != 201: print('Status:', response.status_code, 'Headers:', response.headers, 'Error Response:', response.json()) exit() # Decode the JSON response for the new incident new_incident = response.json() print(new_incident) incident_sys_id = new_incident['result']['sys_id'] # Getting the status of the created incident using its sys_id status_url = f'https://{instance}.service-now.com/api/now/table/incident/{incident_sys_id}' response = requests.get(status_url, auth=HTTPBasicAuth(user, pwd), headers=headers) if response.status_code != 200: print('Status:', response.status_code, 'Headers:', response.headers, 'Error Response:', response.json()) exit() incident_status = response.json() print(incident_status)

This script does the following:

  1. Authenticates with the ServiceNow API using HTTP Basic Authentication.
  2. Retrieves data (which can be used to check if the authentication is successful).
  3. Creates a new incident with short_description and category. You would need to modify this payload based on what fields are mandatory and used in your ServiceNow environment.
  4. Fetches the status of the newly created incident by its sys_id.

Make sure your account has the necessary permissions to perform these actions, and for production code, ensure you handle exceptions and errors appropriately.

ServiceNowOverviewServiceNow is an IT service management platform for recording, tracking, and managing a companys enterprise-level IT processes in a single location.The Datadog ServiceNow integration is a two-way integration that allows you to:Push Datadog-generated events to ServiceNow tickets, as well as manage the resolution workflow from within Datadog through IT service management (ITSM) and IT operations management (ITOM)Use Datadog as a discovery mechanism for ServiceNow Configuration Management Database (CMDB) Configuration Items (CIs) with the service graph connectorEnrich business-specific information stored as CIs in ServiceNow CMDB with your hosts and services information from Datadog, enabling you to better understand your infrastructure usage, accelerate troubleshooting, and maximize resource utilizationDatadog integrates with the following ServiceNow tools:ITOMITSMCMDBNote: The Datadog ServiceNow integration supports ServiceNow releases that are not listed as end of life.CMDB setupService Graph Connector for DatadogService Graph Connector for Datadog can automatically populate server and database configuration items (CIs) in the CMDB for new resources discovered by Datadog. The Service Graph connector is available through the ServiceNow store .For configuration, follow the Service Graph Connectors guided setup instructions.Supported CI Types:ServerAmazon RDSThe notes below only apply if you have already configured the integration for ServiceNow ITOM/ITSM:Service Graph Connector does not use the Target table and Custom table values from the configuration tile. You can save the integration with the Target table default values.The same ITOM/ITSM user can be used for Service Graph Connector by granting this user the role of cmdb_import_api_admin as described in the Service Graph Connectors guided setup instructions.Host taggingEnrich your Datadog hosts with ServiceNow CMDB metadata through host tagging.To enable ingestion of host tags:Configure a Query Builder query in your ServiceNow instance that returns all of the hosts you wish to tag in Datadog.Schedule the query to execute at your desired refresh interval.Once the query has been saved in ServiceNow, go to Datadogs ServiceNow integration tile. Select the Host Tagging tabUnder Query Configuration, click the Add New Row button.Select the ServiceNow Instance and the Query from the dropdown menus.Select a value for the Hostname Column that maps your querys root CI hostname field to Datadogs hostname field.Select any optional field name remapping with Column Name Maps.Click Save.Expect host tags to populate in Datadog shortly after your queries scheduled executions.Monitor the ingestion process in the Datadog Events Explorer by scoping your search query on source:servicenow.TroubleshootingFor host tagging to work correctly, ensure that the following are true in your system:The user who created and executes the Query Builder query matches a username in your Datadog configuration. The user in ServiceNow must have the role cmdb_query_builder_read.The number of results returned by your query must be less than or equal to the glide.cmdb.query.max_results_limit setting in ServiceNow. By default, the maximum number of results is 10000. To change the setting, go to Configuration -> CMDB Properties -> Query Builder Properties.All CIs configured in your Query Builder query must have a 1 label. This ensures you have not created any duplicate CIs, which the parser does not support.LimitationsIngestion is limited to 100k hosts per execution.Updates to hosts are throttled to a few thousand per hour. Take this limit into consideration when choosing your schedule interval.Tagging does not work for Linux machines with lower case host names, because host aliases in Datadog are case sensitive.Service ingestionEnrich your Datadog Service Catalog with ServiceNow CMDB metadata through service ingestion.With service ingestion, you can populate your Datadog Service Catalog with services f

docs.datadoghq.com

ServiceNow is a popular, easy-to-use, ticketing platform that provides automated workflows to replace manual tasks. It has good search capabilities and defined roles, and it allows you to control access to features and capabilities based on those roles. Because it's cloud-based, it's also easily scalable.Developers often need to integrate with ServiceNow because it provides such excellent tools to connect business-to-business systems. For example, it allows easy integration with third-party applications and data sources, which allows you to analyze incidents in more detail. Here is a list of out-of-the-box integrations it offers.In this article, you'll learn how to get incidents from the ServiceNow API using the Python programming language and by using webhooks.The code shown in this tutorial can be found in this GitHub repository.{{blog-cta-100+}}PrerequisitesYou'll need the following to follow along with this tutorial:A ServiceNow account: You need to contact sales to get a real account, but for this tutorial, you could simply use a developer account, which you can sign up for on their website.A personal developer instance: Once you have a developer account, you need to request a Personal Developer Instance (PDI) to access the ServiceNow application. Follow these instructions and make sure you select the Admin role for the PDI.Python version 3.9 or laterA Pipedream account for testing the ServiceNow webhookAnatomy of an IncidentBefore retrieving incidents from ServiceNow, you need to understand their makeup. The best way to understand what constitutes an incident is to create a few using the user interface. Later in this tutorial, you'll then use the ServiceNow API with Python to retrieve them.Log in to Your PDILog in to your PDI using the URL you got after creating it. The URL used for this tutorial, for example, is <code class="blog_inline-code">https://dev139371.service-now.com</code>. It will take you to the login page, where you need to supply your username and password:View and Create IncidentsOnce you're logged in, select All, expand Self-Service, then click on Incidents.This will open the Incidents page, which shows all the current incidents. If you had any, they would be listed here. As you can see below, there are no current incidents:To create an incident, click on the New button in the top left corner. This will open up the page for creating incidents.You have to provide the Urgency, which is a measure of the business criticality based on the impact and business needs of the customer. It's also a way of assigning priority for dealing with incidents. The options here are High, Medium, and Low.You also have to describe your issue. The more information you can provide in this field, the better it is for the support organization to quickly resolve your issue.Since this is only an example, you can use something simple like this:Once you have populated the Urgency and Description, click on Submit to create the incident.As soon as the incident is created, the Incident Details page opens up, which shows other fields such as the Incident Number, Date Opened, and State. This page shows you the details of the incident that you just captured.Create a few more incidents with varying urgencies to use later in this tutorial. See a few examples below:If you go to the Incidents page, you should now see a list of the incidents you just created.How to Retrieve ServiceNow Incidents Using PythonNow you have a few incidents created from the portal, you'll be fetching them using Python.Create a Python Project and Activate a Virtual EnvironmentCreate a new directory and name it <code class="blog_inline-code">Get_Incidents_with_ServiceNow_API</code>.Navigate to the directory and run the following command to create a virtual environment called <code class="blog_inline-code">get_incidents_with_servicenow_api</code>:After creating the virtual environment, you need to activate it. On Windows, run the following command:To activate the virtual

merge.dev

Integrating with ServiceNow Overview Logging trouble tickets Configuring ServiceNow in Applications Manager Prerequisites Steps to configure Configuring Event Preferences Ticket Settings Reopen Settings Update Settings Accessing from Applications Manager Configuration Item Details in CMDB APIs used in APM for incident management in ServiceNow Overview ServiceNow is a web-based Help Desk and Asset Management software. With ServiceNow, you can automatically log trouble tickets for specific alarms and manage incidents from Applications Manager. Logging trouble tickets Applications Manager has the ability to automatically log trouble tickets for specific alarms and to notify the concerned technician when a particular process exceeds the set threshold point. Along with the provision to send emails, SMS messages, and other notifications, alarms can also be tracked by automatically logging trouble tickets in a help desk software. Applications Manager takes care of two-way synchronization of Alerts and Ticket statuses with ServiceNow. For example, you can automatically log a ticket when an alarm is raised, reopen the ticket whenever an alarm reoccurs, or close the ticket if the alarm is cleared. Additionally, the alerts under the Alarms tab include a Ticket Icon that loads the ticket raised when clicked on. Configuring ServiceNow in Applications Manager This section describes the method in which ServiceNow the settings are to be configured in Applications Manager: Prerequisites The ServiceNow user should have the following roles required for the corresponding options for successful integration in Applications Manager: Incident management : itil, itil_admin and personalize_choices CI Sync : itil, itil_admin, personalize_choices and personalize_dictionary Event sync : evt_mgmt_integration Log in to ServiceNow as an admin user and perform the following steps: Go to System Definition and then Tables. Search for "Incident". Click on the entry that has the Label as "Incident". This will load the Incident table. Now, select Controls tab. Enable "Create access controls" and type itil_admin in the "User role" field. Save this table. Steps to configure Under Settingstab, click onAdd-On SettingsunderProduct Settings. An Add-on Settings table is displayed. Click onAddaction for HelpDesk. This takes you to the ManageEngine ServiceDesk Plus Server Details page with a choice to Select HelpDesk Product. Choose ServiceNow. Provide theInstance name (e.g.: [instancename].service-now.com),Username andPassword. Secure connection will be used by default while connecting to ServiceNow and so the protocol must not be specified in the Instance field. Enable the Mail Notification for Connectivity Failure toggle button if you wish to trigger mail notifications in case of connectivity failures. After enabling this option, enter the following details: Configure the email to which the notification has to be sent. You can configure either by choosing Admin email (Mail address configured for the admin user or the mail address in SMTP configuration) or by selecting email actions to be triggered for the selected email from the dropdown. Enable the Append Custom Message checkbox if you want to append customized text messages along with the mail notifcation. Enable the Repeat mails until successful connection checkbox to repeat mail notifications until connection is established successfully. After enabling, specify the Repeat Interval (in minutes) after which mail notification has to be repeated. Enable the Add Events toggle button to configure events. Enabling this option will automatically disable Log Tickets. Either Events or Ticketing can be enabled at a time. By enabling Log tickets toggle button you have the option to configure Ticket Settings. Enable Configuration Item (CI) sync toggle button to configure Configuration Item Settings. Test if the connection is working and save the settings. Configuring Event Preferences For ServiceNow integration, Add Events opti

manageengine.com