About Incidents
Turn a recurring error into an incident, and send it to ServiceNow.
An incident is Integration Mapper’s record that a recurring error needs follow-up. It is opened from a signature in Monitoring: one iFlow and one error, however many times it happened. When ServiceNow is connected, a ticket is created at the same moment.
One incident per error
Section titled “One incident per error”A signature has at most one live incident. Asking again for an incident on the same signature returns the one that exists. After it is resolved, the next request opens a new one.
A signature groups the occurrences of an iFlow by the error the sync recorded, ignoring the parts that change every time, such as message IDs, timestamps and long numbers. For failed messages read from SAP this is usually the status FAILED, and for exception subprocesses the step where it happened; the full SAP text is in each message’s details.
ServiceNow
Section titled “ServiceNow”| Situation | What happens |
|---|---|
| ServiceNow connected and sending on | The ticket is created when the incident is opened, and its number appears in Integration Mapper. |
| The ticket could not be created | The incident shows send failed. Request resend tries again. |
| Sending off, or no active credential | The incident is recorded only in Integration Mapper. |
Integration Mapper creates the ticket and does not read it back: status changes in ServiceNow do not come back, and Mark as resolved in Integration Mapper does not change the ticket.
What it needs
Section titled “What it needs”The Monitoring module. To send tickets, the ServiceNow connection in Settings → Integrations, which needs the Integrations module.