Click through to the Outbound HTTP Request record from the related list on the Transaction. (If you wish, you could also do the same for the Inbound HTTP Request record.)
Your HTTP Request record should look like this:
HTTP Request details:
Integration: < Your Integration >
Connection: < Your Connection >
Transaction: < Your Transaction >
Request state: 'OK' (There are no errors with the HTTP Request.)
Attempt number: < Number of HTTP Request attempts > (Failed requests are retried up to the maximum attempts number as configured on the Integration.)
Endpoint URL: < The external system’s access URL >
Action Method: 'POST'
Request headers: < The header of the request being sent >
Request payload: < The payload of the request being sent >
Status code: '200'
Response headers: < The header of the response being received >
Response payload: < The payload of the response being received >
Compare with the External System's Incident
Navigate to the corresponding Incident in the external system.
Check the values in the fields match those you noted when you saved the Incident in the internal system.
Your external system's Incident record should look like this (depending on the system you're integrating with, your record may look different; the important matter is that the values match):
Resolution code: < Your Resolution code >
Resolution notes: < Your Resolution notes >
Navigate to the Notes tab.
Your Notes tab should look like this:
Activities: < Your Resolution code/notes & State > (added by < your.external.system.user >)
As when testing our previous scenarios, if completing this test after having integrated with the external system (as opposed to connecting to your own instance), it would be good to test the ResolveIncident Message in both directions.
If you have completed this testing for the first time (sending to your own instance only), you are now ready to move on and look at running Build at the Integration level.