> For the complete documentation index, see [llms.txt](https://docs.sharelogic.com/unifi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sharelogic.com/unifi/2.2/integration-guides/incident-attachment-poller-guide/testing/test-outbound-scenarios.md).

# Test Outbound Scenarios

Follow these instructions to test the outbound Message scenarios.

We will create some bonded tickets in the remote instance - initially testing the outbound Message scenarios. Those bonded tickets will then also be available to test the inbound Message scenarios.

## Test CreateIncident

In **native ServiceNow**, navigate to **Incident > Create New**.

The Incident fields to configure are as follows:

|  #  | Field             | Description                                          | Value                     |
| :-: | ----------------- | ---------------------------------------------------- | ------------------------- |
|  1  | Caller            | Person who reported or is affected by this incident. | \<Your Caller>            |
|  2  | Short description | A brief description of the incident.                 | \<Your Short description> |
|  3  | Description       | Detailed explanation on the incident.                | \<Your Description>       |

{% hint style="info" %}
Though the CreateIncident Message has been configured to map more than just the Short Description & Description fields, we have only filled these fields because that is all whe have included in the payload of our Poller.
{% endhint %}

*Your Incident form should look like this:*

![](https://796541950-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MQBk35gIi557UHt7QlJ%2F-MRVw2Lt0WSOI2but1Tk%2F-MRVwv7ZGh-CMHX-aXNX%2FTest%20Outbound%20Scenarios%201.png?alt=media\&token=45dd49e5-eb97-44b4-ac95-49b9f1ed9343)

4\) After you right-click & 'Save', note the Info Message confirming the CreateIncident Message is being sent to your Integration.

5\) Note the Bond is 'Open' and both the Internal & External reference are in place.

{% hint style="success" %}
Repeat as necessary so that there are three bonded tickets in the remote instance:
{% endhint %}

![](https://796541950-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MQBk35gIi557UHt7QlJ%2F-MRVw2Lt0WSOI2but1Tk%2F-MRVxIkvY9vq-4JWTMOY%2FTest%20Outbound%20Scenarios%202.png?alt=media\&token=5d7a9b2c-4337-4fcb-b49b-372fb6c92f6b)

## Test UpdateIncident

**Update one** of the **bonded tickets** in the **originating instance** to cause the UpdateIncident Message to fire:

![](https://796541950-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MQBk35gIi557UHt7QlJ%2F-MRVw2Lt0WSOI2but1Tk%2F-MRVxuQLi1ddzLaDDrCz%2FTest%20Outbound%20Scenarios%203.png?alt=media\&token=8e8252d9-6e00-46e5-84cf-2436998fec2d)

View the Transactions that have been sent. This can be done either in Native ServiceNow, or in the Unifi Operations Portal.

{% tabs %}
{% tab title="Native ServiceNow" %}
Navigate to **\[ws] Unifi > Transport > Transactions**.

![](https://796541950-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MQBk35gIi557UHt7QlJ%2F-MRVw2Lt0WSOI2but1Tk%2F-MRWUVaAHmKcVyQzIxdX%2FTest%20Outbound%20Scenarios%204.png?alt=media\&token=cd495f9e-7cff-48f6-b914-57c7a6855a46)
{% endtab %}

{% tab title="Unifi Operations Portal" %}
Navigate to **\[ws] Unifi > Unifi Operations Portal**.

![](https://796541950-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MQBk35gIi557UHt7QlJ%2F-MRVw2Lt0WSOI2but1Tk%2F-MRWUfKq3n0u9bB_lp5Z%2FTest%20Outbound%20Scenarios%205.png?alt=media\&token=2914b2e1-166b-4825-a65a-0b676bb2ae44)
{% endtab %}
{% endtabs %}

{% hint style="success" %}
We can see that the three CreateIncident messages & one UpdateIncident message have been sent. All are Complete & Accepted & display the relevant Incident & Bond numbers.
{% endhint %}

Confirm the Transaction has updated the **bonded ticket** in the **remote instance**:

![](https://796541950-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MQBk35gIi557UHt7QlJ%2F-MRVw2Lt0WSOI2but1Tk%2F-MRWUxmFTeGjUX4__NB_%2FTest%20Outbound%20Scenarios%206.png?alt=media\&token=a2b86bab-a867-4857-9004-22bc198b88c7)

{% hint style="success" %}
We can see that the update has reached the bonded ticket (& that the correlation id matches the outbound Incident number)
{% endhint %}

## Test ResolveIncident

**Resolve** the **same bonded ticket** in the **originating instance** to cause the ResolveIncident Message to fire:

![](https://796541950-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MQBk35gIi557UHt7QlJ%2F-MRVw2Lt0WSOI2but1Tk%2F-MRWVEQZF17YuPoZe4GN%2FTest%20Outbound%20Scenarios%207.png?alt=media\&token=54a4ce7d-aef9-47ce-866d-5f3b95cfb587)

View the Transactions that have been sent. This can be done either in Native ServiceNow, or in the Unifi Operations Portal.

{% tabs %}
{% tab title="Native ServiceNow" %}
Navigate to **\[ws] Unifi > Transport > Transactions**.

![](https://796541950-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MQBk35gIi557UHt7QlJ%2F-MRVw2Lt0WSOI2but1Tk%2F-MRWVg43L2L5s81PyMhW%2FTest%20Outbound%20Scenarios%208.png?alt=media\&token=48a6c9c8-ec13-456e-b092-d8ed1f5cecd5)
{% endtab %}

{% tab title="Unifi Operations Portal" %}
Navigate to **\[ws] Unifi > Unifi Operations Portal**.

![](https://796541950-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MQBk35gIi557UHt7QlJ%2F-MRVw2Lt0WSOI2but1Tk%2F-MRWVqb_-RKZS2iZdslg%2FTest%20Outbound%20Scenarios%209.png?alt=media\&token=9359fe55-3367-40c6-bccf-8525512b67af)
{% endtab %}
{% endtabs %}

{% hint style="success" %}
We can see that the ResolveIncident messages has been sent. It is Complete & Accepted & displays the relevant Incident & Bond numbers.
{% endhint %}

Confirm the Transaction has updated the **bonded ticket** in the **remote instance**:

![](https://796541950-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MQBk35gIi557UHt7QlJ%2F-MRVw2Lt0WSOI2but1Tk%2F-MRWW29pVymeuB_XsYfb%2FTest%20Outbound%20Scenarios%2010.png?alt=media\&token=77de638d-60b3-4222-a827-94332e520815)

{% hint style="success" %}
We can see that the State, Resolution code & Resolution notes have been updated on the bonded ticket (& that the correlation id matches the outbound Incident number)
{% endhint %}

Navigate to the **Notes** tab to view the Activities stream:

![](https://796541950-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MQBk35gIi557UHt7QlJ%2F-MRVw2Lt0WSOI2but1Tk%2F-MRWWH_i8R81rgGBZDwf%2FTest%20Outbound%20Scenarios%2011.png?alt=media\&token=74485d28-daf6-4aca-affb-87a30ec6d123)

{% hint style="success" %}
We can see that the update has also been logged in the Activities stream.
{% endhint %}

Next, we shall test the **CreateIncidentInbound** Message.