ServiceNow Field Mapping

ℹ️

Need to install in the ServiceNow integration?

Learn how.

“Need to install in the ServiceNow integration? Learn how.”

ServiceNow is complex and highly configurable, so sometimes custom mappings need to be made between FireHydrant's incident fields and ServiceNow's ticket fields.

Ticket types with custom fields need to be mapped to FireHydrant incident fields.

When do I need to configure custom mappings for fields?

There are multiple scenarios where you must configure field mappings for FireHydrant to be able to create tickets in your project(s):

• When you have custom, required fields - If a specific project has any required fields that are not set automatically, especially if they are custom issue fields, then you'll need to configure them in FireHydrant so we know what to set for those fields

How to configure field mapping

Assuming you're in a situation where you must map fields, follow the instructions below.

1. Navigate to the ServiceNow settings page and click on the project you'd like to configure, then selet the Field Mapping tab.
2. Click '+ Add mapping' to create a new mapping.
3. A drawer will come out on the right where you can select between two choices:
   1. Basic mapping allows you to always set fields in ServiceNow to the same values.
   2. Advanced mapping allows conditional logic to map different fields to different values in ServiceNow based on various parameters within FireHydrant.

      📘

      Note:

      Field mappings for a project and its tickets are evaluated and applied upon every incident update. For example, if you have a condition to "set ServiceNow ticket Severity field to SEV1 whenever the incident is is SEV1, otherwise default to SEV3," this will evaluate each time you make updates on the incident so that if the severity is escalated/de-escalated, the field in ServiceNow will change accordingly.

4. You can select a ServiceNow field once you've selected between basic vs. advanced mapping.
   1. If Basic, you can set the field's value, and this will apply each time you create the ticket and whenever any detail on the incident is updated.
   2. If Advanced, you can select conditions and values that should apply when those conditions are met, along with an Else default value if no conditions are met.
5. For values, you will see the following:
   1. You can choose between preset FireHydrant parameters and "Use a custom value." If you select Custom Value, you can input any value you'd like, and the field will also support Template Variables. Note that what you can insert as a custom value will depend on the field's settings in ServiceNow.
6. Once this field's mapping has been configured to your liking, click Save to persist. Rinse and repeat these steps for all fields you'd like to map.

Advanced mapping conditions

The following conditions are available for configuring advanced if/else if/else rules in ServiceNow Field mapping:

• Current severity - Current incident's severity
• Current milestone - Current incident's milestone
• Incident name
• Incident number
• Incident description
• Ticket priority - Priority of the Follow-up created on FireHydrant (not Incident)
• Ticket tags - Tags of the Follow-up created on FireHydrant (not Incident)
• Incident impacted infrastructure - Which Service Catalog components are impacted on an incident
• [Custom Fields] - Any Incident Custom Fields configured by users
• Entered [milestone] at - If timestamp for the specified milestone exists and has been filled in

Common ServiceNow field mappings

Impact and Urgency matrix
ServiceNow uses a matrix for impact and urgency to visually represent the priority of an incident or issue by considering both the severity of its potential impact on business operations ("impact") and the time sensitivity of resolving it ("urgency"), allowing for a more nuanced assessment of how quickly a problem needs to be addressed based on its potential consequences.

You can set up field mapping in FireHydrant to match your ServiceNow impact and urgency matrix, Using custom fields in FireHydrant.

Create Impact and Urgency custom fields:

In the FireHydrant UI navigation, select Settings and then Incident settings. On the top right, click "+ Add custom field".

1. Display name (required): Set the display name to be either Impact or Urgency
2. Help text: A helpful description for completing the field that appears in tooltips in the web and Slack for your responders
3. Type (required): set this to be theMulti-select type.
   1. Enter the following values for 1, 2, and 3
4. Field Settings: Specifies whether the field is required and/or should be immediately visible on the declaration form for users.

Set up Impact and Urgency field mapping

1. Navigate to the ServiceNow settings page and click on the project you'd like to configure, then the Field Mapping tab.
2. Click '+ Add mapping' to create a new mapping.
3. A drawer will come out on the right; select the Basic Mapping option
4. Select either Impact or Urgency from the ServiceNow dropdown
5. Map that field to the custom field set up from the FireHydrant dropdown
6. Custom Fields in FireHydrant will be prepended with "Incident". Impact will display as Incident Impact in the dropdown.