> 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/3.1/integration-guides/incident-attachment-poller-guide/testing/test-createincidentinbound.md).

# Test CreateIncidentInbound

## Create Test Incident

In **your PDI**, navigate to **Incident > Create New**.

The Incident fields to configure are as follows:

<table><thead><tr><th width="150">Field</th><th width="277.5604952166573">Description</th><th>Value</th></tr></thead><tbody><tr><td>Caller</td><td>Person who reported or is affected by this incident.</td><td>&#x3C;Your Caller></td></tr><tr><td>Impact</td><td>Measure of the business criticality of the affected service.</td><td>&#x3C;Your Impact></td></tr><tr><td>Urgency</td><td>The extent to which resolution of an incident can bear delay.</td><td>&#x3C;Your Urgency></td></tr><tr><td>Assignment group*</td><td>The group to which the ticket is assigned.</td><td><em>&#x3C;</em>Your Assignment group></td></tr><tr><td>Short description</td><td>A brief description of the incident.</td><td>&#x3C;Your Short description></td></tr><tr><td>Description</td><td>Detailed explanation on the incident.</td><td>&#x3C;Your Description></td></tr></tbody></table>

{% hint style="info" %}
*\*Assignment group: This should be the group you created in your PDI to enable Unifi to identify which newly created, non-bonded tickets to poll and whose sys id was stored in a connection variable and passed into the Setup Script of the Poll Processor.*
{% endhint %}

*Your Incident form should look like this:*

![](/files/-MgyZrUJK93CgG9zg3U2)

{% hint style="success" %}
Note the values entered (including State), so that you can check them against the mapped fields on the corresponding record in the instance being integrated to.
{% endhint %}

You should now have a non-bonded ticket in the remote instance *(assigned to \<Your Assignment group>)*:

![](/files/-Mgy_c1vtkxQ6Dj7tv8V)

## Poll for Creates

In **Unifi Integration Designer**, click on the **'Pollers' icon**. Navigate to & **open** **< Your Create Poller >** *(created on the* [*'Poller' page of the Incident Create Poller Guide*](/unifi/3.1/integration-guides/incident-create-poller-guide/polling/poller.md#new-poller)*)*. & click **Execute Now**:

![](/files/-MgyaQVCbtGCOeXp3e6t)

In **native ServiceNow**, navigate to **Unifi > Polling > Poll Requests**. Click to **Open** & view the generated **Poll Request**. Confirm that only the one Incident was found (this is exactly as we expect because we are only polling for Incidents assigned to a specific Assignment group):

![](/files/-MgycX55vGkSfc3lp8tj)

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

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

![](/files/-MgydxS1EcEmsur-3iK2)
{% endtab %}

{% tab title="Unifi Operations Manager" %}
Navigate to **Unifi > Unifi Operations Manager**.

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

{% hint style="success" %}
We can see the CreateIncidentInbound message has been received. It is Complete & Accepted and displays the relevant Incident & Bond numbers.
{% endhint %}

Confirm the following:

The Transaction has created the **bonded ticket** in **this instance**.

*Your new Incident should look like this:*

![](/files/-Mgygg7GH14D5-vblEAD)

{% hint style="info" %}
The calller\_id was populated with the default value `gs.getUserID()` because the table API was returning display\_value instead of value. If the Create Poller was active and running then the caller\_id would be the Integration User. Because the Create Poller was manually executed whilst inactive, then the value is the user who executed the poll.
{% endhint %}

The Transaction has updated the **bonded ticket** in the **remote instance (your PDI)** *(with the correlation id)*.

*Your originating Incident should look like this:*

![](/files/-MgyhRYMi9jGRJpZzSFJ)

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