ServiceNow
Keep incidents in step between ServiceNow and Aegis, and push a chosen Aegis incident to ServiceNow.
At a glance
| Direction | Both ways. |
|---|---|
| What it brings in | ServiceNow incidents, optionally only those changed since a date. Outbound, a chosen Aegis incident is created in ServiceNow, or updated when it is already linked. |
| Where it lands | Incidents, linked to the ServiceNow record. |
| Credentials and permissions |
Your instance address and an OAuth application from
System OAuth → Application Registry (client ID and
secret) with the redirect address shown on the connector page; an
administrator signs in with Authorize with ServiceNow.
The signing-in ServiceNow account needs to read and write incidents.
|
| Owner of imported records | The person who ran the sync. |
| When it runs | On demand from the connector page or the API. |
| Set it up |
/connectors/servicenow, by people allowed to configure
connectors, on a plan that includes the connector.
|
Good to know
- An incident that came from ServiceNow is not pushed back as a duplicate; push it with update to change the existing record.
Where this connects
Incidents are handled in Incidents.