ServiceNow ticketing
With ServiceNow connected, Raise Ticket appears on every event. One click creates an incident in the client’s own ServiceNow instance with the event details filled in.
This page describes the connector settings. To raise a ticket from an event, see Raise a ticket. To connect ServiceNow step by step, see Connect ServiceNow.
Who can use it
Section titled “Who can use it”| Requirement | Detail |
|---|---|
| Plan | Super |
| Switched on for the workspace | ITSM ticketing must show a tick under Policies, in the Feature flags list. It is on by default for a Super workspace. |
| Role to set it up | Admin. ITSM appears under Workspace in the sidebar for admins only. |
| Role to raise a ticket | Admin or member. Viewers cannot. |
What ServiceNow needs
Section titled “What ServiceNow needs”- The Washington DC release or newer.
- The system property
glide.oauth.inbound.client.credential.grant_type.enabledset totrue. - An OAuth application registered under System OAuth → Application Registry as an Application endpoint for external clients. Leave it confidential, not public.
- An OAuth Application User on that registry record, with the
itilrole. ServiceNow creates the incidents as that user.
Identiguard signs in to ServiceNow with the OAuth client, using the client-credentials grant. The client ID and secret are stored encrypted.
The ServiceNow connection card
Section titled “The ServiceNow connection card”The ITSM page has one card, ServiceNow connection.
| Control | What it does |
|---|---|
| Enable ticketing | A tick box. When ticked and saved, Raise Ticket is shown on the event feed for this workspace. |
| ServiceNow instance URL | The address of the instance, for example https://your-instance.service-now.com. It must use HTTPS and be on service-now.com or servicenowservices.com. |
| OAuth client ID and OAuth client secret | The credentials of the OAuth application. Once saved, the card shows them masked, with Replace. |
| Assignment group | Optional. Routes every incident to one queue. Enter a group name, which Identiguard looks up on the instance, or a sys_id, which is used as it is. |
| Caller sys_id | Optional. The ServiceNow user recorded as the caller. |
| Save changes | Saves the card. The button shows Saving… |
| Send test incident | Creates a test incident in ServiceNow. Available once the connector is saved. |
| Disconnect | Removes the connector and deletes the stored OAuth client |
The messages are ServiceNow connector saved., Test incident with the incident number created in ServiceNow. and ServiceNow disconnected.
The test incident is titled “Identiguard connection test - no action required” and has the severity INFO. Close it in ServiceNow after you have seen it.
Change the credentials or the instance
Section titled “Change the credentials or the instance”- To change the client ID and secret, choose Replace, enter both and save.
- If you change the ServiceNow instance URL, the card asks for the client ID and secret again. It explains: “Changing the instance URL means re-entering the OAuth client ID and secret. The stored client is only ever sent to the instance it was saved for.”
Stop ticketing
Section titled “Stop ticketing”| To | Do this |
|---|---|
| Hide Raise Ticket but keep the connector | Untick Enable ticketing and choose Save changes |
| Remove the connector | Choose Disconnect. The dialog Disconnect ServiceNow? explains that the event feed stops offering ServiceNow tickets immediately and that the stored OAuth client is deleted. Incidents already raised are not affected. Choose Disconnect to confirm. |
When Raise Ticket appears
Section titled “When Raise Ticket appears”Raise Ticket is shown on each event row and in the event detail when all of these are true:
- The workspace is on Super and ITSM ticketing is on.
- An admin has saved the ServiceNow connector.
- Enable ticketing is ticked and saved.
A viewer sees the button disabled.
When the ticket is created you see ServiceNow incident with the number created. The button shows Raising… while it works.
What a ticket contains
Section titled “What a ticket contains”| ServiceNow field | Content |
|---|---|
| Short description | “Identiguard:” followed by the event message, or the event type when there is no message. At most 160 characters. |
| Description | Tenant name, who raised it, tenant ID, event ID, source, severity, event time and a link to the workspace’s event list |
| Urgency and impact | Set from the event severity. See the table below. |
| Correlation ID | A value that identifies the Identiguard event, so the service desk can recognise the same event raised twice |
| Assignment group | The group from the connector, if you set one |
| Caller | The caller from the connector, if you set one |
Severity to urgency and impact
Section titled “Severity to urgency and impact”| Identiguard severity | ServiceNow urgency | ServiceNow impact |
|---|---|---|
CRITICAL |
1 | 1 |
ERROR |
2 | 2 |
WARN |
3 | 2 |
INFO |
3 | 3 |
DEBUG |
3 | 3 |
ServiceNow works out the incident priority from urgency and impact with its own rules.
Tickets for journey outages
Section titled “Tickets for journey outages”When ticketing is on, a confirmed journey outage also opens a ServiceNow incident automatically.
- The short description starts with “[DOWN]” and names the tenant and the journey.
- The description gives the failure reason, the number of failed probes in a row, the region and the time the failure started.
- Urgency is 2 and impact is 2.
- When the journey recovers, Identiguard adds a work note to the incident. It does not close the incident. Closing it is the service desk’s decision.
Other ticketing tools
Section titled “Other ticketing tools”ServiceNow is the only ticketing connector for clients today. If a client uses another tool, the usual answer is to send alerts to Slack, Teams or email and let that tool pick them up from there.
Troubleshooting
Section titled “Troubleshooting”The page and the form
Section titled “The page and the form”| What you see | Why | What to do |
|---|---|---|
| ITSM is not in the sidebar, or The ITSM connector is not available on this workspace plan. | The workspace is not on Super, or ITSM ticketing is off for the workspace. | Upgrade to Super, or ask a platform operator. |
| Forbidden: only workspace admins can manage the ITSM connector. | You are not an admin. | Ask an admin. |
| ServiceNow instance URL is required., …is invalid., …must use HTTPS. or …host is not allowed. | The URL is empty, is not HTTPS, or is not on service-now.com or servicenowservices.com. |
Correct the URL. |
| clientId and clientSecret must be provided together., clientId and clientSecret are required when configuring ServiceNow. or ServiceNow credentials are not configured. | One or both credentials are missing. | Enter both the client ID and the secret. |
| Changing the ServiceNow instance URL requires re-entering the OAuth client ID and secret. or The stored ServiceNow client belongs to a different instance URL. Re-enter the OAuth client ID and secret. | The instance URL changed. | Enter the client ID and the secret again. |
| ServiceNow is not configured for this workspace. | You tested or raised a ticket before the connector was saved. | Save the connector first. |
| The ServiceNow connector is turned off for this workspace. | Enable ticketing is not ticked. | Tick it and save. |
| Failed to save the ServiceNow connector. or ServiceNow test failed. | The server gave no usable message. | Try again. If it continues, tell support the time and the page. |
Messages from ServiceNow
Section titled “Messages from ServiceNow”These messages include the HTTP status that ServiceNow returned. Identiguard reports the status only, so the causes below are the usual ones.
| What you see | Why | What to do |
|---|---|---|
| ServiceNow authentication failed with a status and a reason | The client ID or secret is wrong, the client is public, the client-credentials grant is not enabled, the release is older than Washington DC, or the registry record has no OAuth Application User. | Check each item in What ServiceNow needs. |
| A message ending the instance redirected the request, and redirects are not followed | Something in front of the instance redirects the request, or the URL is wrong. | Use the direct instance URL. |
| ServiceNow did not return an access token. | The token endpoint answered without a token. | Check the application registry record. |
| ServiceNow assignment group lookup failed with a status | The OAuth user cannot read groups. | Give the user read access to groups, or enter the group’s sys_id. |
| ServiceNow assignment group with the name was not found on the instance. | The group name is wrong. | Correct the name, or paste the sys_id. |
| ServiceNow incident creation failed with a status | Usually the OAuth Application User has no itil role, the caller sys_id is wrong, or a mandatory field rule on the instance refused the incident. |
Fix the role or the field on the instance. |
Problems when you raise a ticket from an event are in Raise a ticket.