ServiceNow - Create Incident per Asset

ServiceNow - Create Incident per Asset creates an incident in ServiceNow for each entity that matches the parameters of the saved query supplied as a trigger (or from the entities selected in the asset table).

General Settings

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 drop-down is available, and you can choose which adapter connection to use for this Enforcement Action.

Required Fields

These fields must be configured to run the Enforcement Set.

1. Incident short description - Specify the incident title.
2. Message severity (default: info) - Select the message severity: info, warning or error.
3. Instance Name - The Axonius node to use when connecting to the specified host. For more details, see Connecting Additional Axonius Nodes.

Additional Fields

These fields are optional.

1. ServiceNow domain (optional) - URL for the ServiceNow admin panel.

   NOTE

   If Use stored credentials from the ServiceNow adapter is disabled, this field is required.

2. User name and Password - To connect to ServiceNow, you will need to create a user with action privileges.

   NOTE

   If Use stored credentials from the ServiceNow adapter is disabled, these fields are required.

3. Verify SSL - 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.

4. HTTPS proxy - Connect the adapter to a proxy instead of directly connecting it to the domain.

5. Incident description and Map Axonius fields to fields in the description - These fields allow you to create custom incident descriptions. In Incident description, enter a description template that includes field placeholders for field mapping. The placeholder is enclosed by double {{ }}. Then, in Map Axonius fields to fields in the description, enter the field placeholder in Placeholder text fields on the left and select an Axonius field in Axonius fields on the right. The value of the Axonius field is populated into the description in place of the placeholder text.

   In the example below, the template in Incident description maps the fields selected under Axonius fields into the placeholders dev_hostname, dev_ip, and dev_serial. Each asset that matches the query parameters will have its data added to the incident description.

   

6. Multiple optional incident related settings:

   1. Incident Type
   2. Caller ID
   3. Requested for
   4. Symptom
   5. Assignment group
   6. Category
   7. Subcategory
   NOTE

   Since the valid values of these parameters are customer specific, Axonius does not validate any of these parameter's values. You must make sure inserted values are correct, otherwise, the request might fail.

7. Additional fields (optional, default: empty) - Specify additional fields to be added as part of the incident as key/value pairs in a JSON format.
   For example:

   {"field1": "value1", "field2": "value2"}.
   

   • If supplied, Axonius will add the specified fields and values to the created incident. If one of the specified fields is invalid, the request might fail.

8. Table name (optional, default: incident) - Specify the ServiceNow table name in which the incident will be created.

   • If supplied, the incident will be created in the specified table name.
   • If not supplied, the incident will be created in the 'incident' table.

9. Axonius to ServiceNow field mapping - Field mapping allows you to map Axonius fields to the CMDB fields. The input should be key/value pairs in a JSON format.
   For example:

   {"axonius_field1":"servicenow_field1", "axonius_field2":"servicenow_field2"}