> 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-multiple-message-poller-guide/testing/test-updateincidentinbound.md).

# Test UpdateIncidentInbound

To test our integration we will need some bonded tickets in the remote instance. If there aren't any already in place, then they'll need to be created.

## Create Test Incidents

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/-MRL1oVXzK5oqGSlp5gS)

4\) 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 two or three bonded tickets in the remote instance:
{% endhint %}

![](/files/-MRL273gvTF5XZ0ZF-80)

## Update from Originating Instance

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

![](/files/-MRL2HrqP4zB2IN63uKS)

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/-MRL2vEwZsjoDz0CqhGV)
{% endtab %}

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

![](/files/-MRL3EL--rce3YZnmKHP)
{% 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/-MRL3h5_iMuKHTmJzYUw)

![](/files/-MRL3lFW2XgFVdzCMRt0)

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

## Poll for Updates

In **Unifi Integration Designer**, click on the **'Pollers' icon**. Navigate to & **open** **< Your Poller >** *(created earlier)*. Click **Execute Now**:

![](/files/-MRL4FvLww202wFnDz1w)

In **native ServiceNow**, navigate to **\[ws] Unifi > Polling > Poll Requests**. Click to **Open** & view the generated **Poll Request**. Confirm that no Incident was found (this is exactly as we expect because we are only polling for updates made by the remote instance):

![](/files/-MRL4Q8o9h7qlwOZvJne)

## Update from Remote Instance

in the **remote instance**, **update two** of the **bonded tickets** in turn.

{% hint style="info" %}
Updates have been made to the Description field only. Correlation ID is highlighted for us to identify the correct bonded ticket.
{% endhint %}

{% tabs %}
{% tab title="First Ticket" %}
![](/files/-MRL5IjNhgtoPJL6QEzR)
{% endtab %}

{% tab title="Second Ticket" %}
![](/files/-MRL5N3qrvuvfJkvKVB4)
{% endtab %}
{% endtabs %}

## Poll for Updates

Back in the **originating instance**, navigate to & **open < Your Poller >**. Click **Execute Now**.

**Open** the **corresponding Poll Request** & **confirm** that **both Incidents** were **found** (and *only* those) and that the **Message name** was **UpdateIncidentInbound**:

![](/files/-MRL5a_zX8D13PGBPbQ3)

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/-MRLAZkToNoXf3sekyk9)
{% endtab %}

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

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

{% hint style="success" %}
We can see that two UpdateIncidentInbound messages have been received. Both are Complete & Accepted & display the relevant Incident & Bond numbers.
{% endhint %}

Confirm the Transactions have updated the **bonded tickets** in the **originating instance**.

{% tabs %}
{% tab title="First Ticket" %}
![](/files/-MRLBTuo-Scum8NdkLHK)

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

{% tab title="Second Ticket" %}
![](/files/-MRLBnxcTrcwhFg5rVpv)

![](/files/-MRLBre-iHYHRxUJjO19)
{% endtab %}
{% endtabs %}

## Challenge

For completeness, to prove we are only querying and pulling back data from bonded records, update an incident in the remote system which isn't bonded (Correlation ID is empty) & run the Poller again.

What do you expect to happen?

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