ServiceNow - Create Incident per Asset
  • 22 Nov 2022
  • 3 Minutes to read
  • Dark
    Light
  • PDF

ServiceNow - Create Incident per Asset

  • Dark
    Light
  • PDF

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).

See Creating Enforcement Sets for more information on adding Enforcement Actions to Enforcement Sets.

General Settings

  1. Enforcement Set name (required) - The name of the Enforcement Set. A default value is added by Axonious. You can change the name according to your needs.
  2. Add description (optional) - Click to add a description of the Enforcement Set. It is recommended to describe what the Enforcement Set does.
  3. Run action on assets matching following query (required) - Select an asset category and a query. The Enforcement Action will be run on the assets that match the query parameters.

Required Fields

These fields must be configured to run the Enforcement Set.

  1. Action name - The name of the Main action. A default value is added by Axonious. You can change the name according to your needs.
  2. Configure Action Conditions - Toggle on to enter a condition statement. See Configuring Enforcement Action Conditions for more information about condition statement syntax.

  1. Use stored credentials from the ServiceNow adapter - Select this option to use the first connected ServiceNow adapter credentials.
    NOTE
    To use this option, you must successfully configure a ServiceNow adapter connection.
  2. Incident short description - Specify the incident title.
  3. Message severity (default: info) - Select the message severity: info, warning or error.

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 (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](../certificate-settings#ssl-trust-ca-settings).

  4. HTTPS proxy (optional) - Enter a proxy to use when connecting to the value supplied in Host Name or IP Address. If no value is supplied, Axonius connects directly to the value supplied in Host Name or IP Address.

  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 Description fields on the left and select an Axonius field on the right. The value of the Axonius field is populated into the description in place of the placeholders.

    For example, the template in Incident description maps the fields selected under Axonius fields into the placeholders dev_hostname, dev_ip, and dev_serial.

    ECDescriptionFieldMapping.png

  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"}
    

To learn more about configuring Enforcement Sets, see Configuring Enforcement Sets.


Changing your password will log you out immediately. Use the new password to log back in.
First name must have atleast 2 characters. Numbers and special characters are not allowed.
Last name must have atleast 1 characters. Numbers and special characters are not allowed.
Enter a valid email
Enter a valid password
Your profile has been successfully updated.