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

# Test CreateIncidentInbound

Follow these instructions to test the CreateIncidentInbound Message.

## Create Test Incident

In **your PDI**, 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  | Impact             | Measure of the business criticality of the affected service.  | \<Your Impact>                 |
|  3  | Urgency            | The extent to which resolution of an incident can bear delay. | \<Your Urgency>                |
|  4  | Assignment group\* | The group to which the ticket is assigned.                    | *<*&#x59;our Assignment group> |
|  5  | Short description  | A brief description of the incident.                          | \<Your Short description>      |
|  6  | Description        | Detailed explanation on the incident.                         | \<Your Description>            |

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

![](https://2404534899-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MQBk35gIi557UHt7QlJ%2F-MgvDHo9EgnBoFsC607I%2F-MgyZrUJK93CgG9zg3U2%2FIAPG%20-%20Test%20CreateIncidentInbound%201.png?alt=media\&token=d7d13a57-f268-41a3-b6b6-5b024aa4765d)

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

![](https://2404534899-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MQBk35gIi557UHt7QlJ%2F-MgvDHo9EgnBoFsC607I%2F-Mgy_c1vtkxQ6Dj7tv8V%2FIAPG%20-%20Test%20CreateIncidentInbound%202.png?alt=media\&token=dcda7c90-e995-4ceb-96fb-f229bf0b596a)

## 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.0/integration-guides/incident-create-poller-guide/polling/poller.md#new-poller)*)*. & click **Execute Now**:

![](https://2404534899-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MQBk35gIi557UHt7QlJ%2F-MgvDHo9EgnBoFsC607I%2F-MgyaQVCbtGCOeXp3e6t%2FIAPG%20-%20Test%20CreateIncidentInbound%203.png?alt=media\&token=a2477d0f-7cea-49ac-a02b-7db2ecc8994b)

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

![](https://2404534899-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MQBk35gIi557UHt7QlJ%2F-MgvDHo9EgnBoFsC607I%2F-MgycX55vGkSfc3lp8tj%2FIAPG%20-%20Test%20CreateIncidentInbound%204.png?alt=media\&token=b43328da-91a6-4cdd-941a-709b6e6e0eab)

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

![](https://2404534899-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MQBk35gIi557UHt7QlJ%2F-MgvDHo9EgnBoFsC607I%2F-MgydxS1EcEmsur-3iK2%2FIAPG%20-%20Test%20CreateIncidentInbound%205.png?alt=media\&token=9f528498-5108-47f9-ad92-2b51126f04af)
{% endtab %}

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

![](https://2404534899-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MQBk35gIi557UHt7QlJ%2F-MgvDHo9EgnBoFsC607I%2F-MgyeN3M1V4rwStKNlT3%2FIAPG%20-%20Test%20CreateIncidentInbound%206.png?alt=media\&token=f3be37ed-a747-45d9-9a7d-9a125e00b420)
{% 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:*

![](https://2404534899-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MQBk35gIi557UHt7QlJ%2F-MgvDHo9EgnBoFsC607I%2F-Mgygg7GH14D5-vblEAD%2FIAPG%20-%20Test%20CreateIncidentInbound%207.png?alt=media\&token=ec6bf960-8b72-4d3c-a411-8dfb10d65295)

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

![](https://2404534899-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MQBk35gIi557UHt7QlJ%2F-MgvDHo9EgnBoFsC607I%2F-MgyhRYMi9jGRJpZzSFJ%2FIAPG%20-%20Test%20CreateIncidentInbound%208.png?alt=media\&token=dec0c98d-12f4-4d2b-b8d1-6568ea5c7cfc)

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