This
screen displays the details of an exception.
Table 1. Exception details screen, error
| Actions |
Description |
| Ignore |
This action button ignores the exception whose details you're
viewing. Once an exception is ignored, the error cannot be reprocessed. |
| Reprocess |
This action button submits the exception for reprocessing by
an Integration Adapter. Note: Only exceptions in Initial
or Saved states can be reprocessed. Reprocessing could result in another
error if the API fails again.
|
| Fields |
| Integration
Error ID |
The unique ID of the integration exception. |
| Service Name |
The service from which the exception was generated. |
| Sub Service Name |
The sub-service that caused the exception upon execution. |
| Queue ID |
The queue the exception was assigned to. |
Table 2. Exception details screen, input XML
| The API's input XML is displayed
in the text area. To save modified exceptions so
that they may be submitted and reprocessed at a later time, make the
necessary changes to the input XML and click Save.
|
Table 3. Exception details screen, error XML
| The API's error XML is displayed
in the text area. |
Table 4. Exception details screen, error history
| Fields |
Description |
| Error ID |
The unique ID of the exception. |
| Input XML |
Link to the API's input XML. |
| Error XML |
Link to the error XML generated by the API. |
| Created On |
The date the exception was created. |
| Queue ID |
The queue the exception was assigned to. |
| Exception State |
The state of the exception. Can be Initial, Modified, Fixed,
or Ignored. |
| Error Code |
The error code for this exception. |
| Error Message |
The error message for this exception. |