ServiceNow - Update Tickets

ServiceNow - Update Tickets modifies existing tickets in ServiceNow that are related to:

📘

Note

The ServiceNow API returns a 200 status code upon successful procession of the request. However, if the syntax of a field like incident_state is incorrect (for example, has a lowercase first letter), the update fails without any error message from the API. Therefore, it is crucial to ensure that all field values passed to ServiceNow adhere to the correct syntax. To mitigate this, you can write a JSON expression in Additional fields (json format) under the Additional Fields section below to precisely define the values being sent, including case sensitivity.

Required Fields

These fields must be configured to run the Enforcement Set.

• Use stored credentials from ServiceNow adapter - Select this option to use the ServiceNow connected adapter credentials.
  • When you select this option, the Select Adapter Connection dropdown is available, and you can choose the adapter connection to use for this Enforcement Action.

📘

Note

To use this option, you must successfully configure a ServiceNow adapter connection.

• Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Working with Axonius Compute Nodes.

Connection And Credentials

These fields are optional.

💡

Connection and Credentials

When Use stored credentials from the adapter is toggled off, some of the connection fields below are required to create the connection, while other fields are optional.

• ServiceNow Domain - The full URL for your ServiceNow instance.

• User Name and Password - To connect to ServiceNow, you need to create a user with action privileges to create and manage assets.

• OAuth Client ID and OAuth Client Secret - The credentials for OAuth-based access to ServiceNow. Refer to OAuth 2.0 with Inbound REST for full details on how to obtain the OAuth Token.

• OAuth Refresh Token - When using the OAuth method of authentication, enter the value of the Refresh Token issued by a ServiceNow instance. This token is used to obtain new access tokens without requiring the user to reauthenticate.

• OAuth Custom Endpoint Path - Specify a custom endpoint path to be used instead of the default oauth_token.do.

• Enable sending OAuth requests as JSON - Enable sending the request in JSON format instead of the standard www-form-urlencoded format.

• Apigee URL - The URL of the domain that the GET request is sent to for acquiring the Apigee token.

• Resource Apigee - The specific resources that the Apigee token is configured to access.

• Verify SSL (optional) - Select whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings.

• HTTPS Proxy (optional) - Connect the adapter to a proxy instead of directly connecting it to the domain.

Ticket Additional Settings

These fields are optional.

• Additional fields (json format) - Specify additional ServiceNow fields and their values as key/value pairs in JSON format. This is particularly useful for setting fields that are not explicitly listed above or for ensuring the correct syntax (including case sensitivity) of values such as incident_state.

  Example:

   { "close_notes" : "Vulnerability Remediated by Axonius EC Action",
  "incident_state" : "Resolved",   
   "close_code": "Duplicate" }
  

• Map Axonius fields to adapter fields - Use the Field Mapping Wizard to map Axonius fields to fields in external systems. In this way, you can transfer data found in Axonius into the external system as part of the configuration of relevant enforcement actions. The wizard shows you which fields exist on the Axonius system, allowing you to map them easily.

  📘

  Note:

  For details, see Axonius to External Field Mapping.

📘

Note

When Fetch dynamic dropdown values is enabled for the ServiceNow adapter connection, Placeholder text fields (within the Field Mapping Wizard) will be populated with the available field names from ServiceNow.

Ticket Main Settings

These fields are optional.

• Ticket Status - The status to set for the ServiceNow ticket.

📘

Note

To populate the available options in the Ticket Status dripdown directly from the ServiceNow adapter, enable the Fetch dynamic dropdown values option in your ServiceNow adapter's Advanced Configuration.

• Ticket Assignee - The ServiceNow user assigned to process the ticket.
• Ticket Comments - Free-form text to add as a comment in the ServiceNow ticket.

• Update tickets using CSV attachment - When enabled, the CSV attachment on an existing ticket will be updated with a new CSV file. The old file is overwritten.

Required Permissions

---