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

<table><thead><tr><th width="165.27943113633063">Field</th><th width="301.2776203966006">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>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" %}
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/-Mgv20L32OxJKtj4WNkH)

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

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

## Test UpdateIncident

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

![](/files/-Mgv4UsIxMbo5kBLP2Wn)

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

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

![](/files/-Mgv6-xGHJO_cwPTXnhk)
{% 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/-Mgv7WfxkiNEnyaWOgGX)

{% 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/-Mgv9POwOJQFy4e4YcnY)

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

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

![](/files/-MgvAYiA7GEFYJfmaAYp)
{% 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/-MgvBka0kiv9lLJaQ0uY)

{% 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/-MgvDBE2sdGtKWHkjdHB)

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


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sharelogic.com/unifi/3.1/integration-guides/incident-attachment-poller-guide/testing/test-outbound-scenarios.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
