> 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

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:*

![](/files/-MRVwv7ZGh-CMHX-aXNX)

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 %}

![](/files/-MRVxIkvY9vq-4JWTMOY)

## Test UpdateIncident

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

![](/files/-MRVxuQLi1ddzLaDDrCz)

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**.

![](/files/-MRWUVaAHmKcVyQzIxdX)
{% endtab %}

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

![](/files/-MRWUfKq3n0u9bB_lp5Z)
{% 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**:

![](/files/-MRWUxmFTeGjUX4__NB_)

{% 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:

![](/files/-MRWVEQZF17YuPoZe4GN)

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**.

![](/files/-MRWVg43L2L5s81PyMhW)
{% endtab %}

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

![](/files/-MRWVqb_-RKZS2iZdslg)
{% 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**:

![](/files/-MRWW29pVymeuB_XsYfb)

{% 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:

![](/files/-MRWWH_i8R81rgGBZDwf)

{% 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.