> 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-update-poller-guide/inbound-message/updateincidentinbound-message.md).

# UpdateIncidentInbound Message

## New Message Modal

Click the **'Messages' icon**, then **New**.

The fields to be configured for the UpdateIncidentInbound New Message modal are as follows:

<table><thead><tr><th width="177.33333333333331">Field</th><th width="333.12240184757513">Description</th><th width="219.56906516759452">Value</th></tr></thead><tbody><tr><td>Message name</td><td>The message name that is unique for this integration.</td><td>'UpdateIncidentInbound'</td></tr><tr><td>Type</td><td>The primary purpose of the message.</td><td>'Update'</td></tr><tr><td>Direction</td><td>The direction(s) this message is configured to support.</td><td>'Inbound'</td></tr><tr><td>Description</td><td>The description for this message and the requirement it is meeting.</td><td>&#x3C;Your description></td></tr></tbody></table>

*Your UpdateIncidentInbound New Message modal should look like this:*

![](/files/-Mf3LayxF4mMsY9UWW6W)

Click **Submit and view** to further configure the Message.

## Response Fields

Navigate to **Message > Response**.

The Response fields to be configured are as follows:

<table><thead><tr><th width="150">Field</th><th width="373.18863302302793">Description</th><th>Value</th></tr></thead><tbody><tr><td>Response</td><td>The immediate synchronous response to this message.</td><td>lookup: 'Response'</td></tr><tr><td>Async*</td><td>Turn this option on if you want inbound processing to occur asynchronously or this message is the first of an asynchronous message pair.</td><td>&#x3C;false></td></tr></tbody></table>

*\*This field is automatically defaulted to true.*

{% hint style="info" %}
The 'Response' Message was previously configured *(in the Outbound Incident Guide)* to apply in an 'Inbound' direction. Change it to 'Bidirectional'.
{% endhint %}

*Your Response form should look like this:*

![](/files/-Mf3Mj9Cb0A8L_UAG-vj)

Navigate to **Message > Bond**.

## Bond Fields

The Bond fields to be configured are as follows:

<table><thead><tr><th width="150">Field</th><th width="365.10674408217955">Description</th><th>Value</th></tr></thead><tbody><tr><td>Bond ownership*</td><td>Determine if the sender should own the bond or not in order for this message to be processed? Use 'Ignore' to process regardless of the owner flag.  <em>(Choices: Ignore, Must own, Must not own.)</em></td><td>'Ignore'</td></tr><tr><td>Bond condition type*</td><td>The type of conditional check made on the bond. (<em>None:</em> no checks are made. <em>State:</em> checks against the state are made using the conditional checkboxes. <em>Scripted:</em> the 'Bond condition' script is used.)</td><td>'State'</td></tr><tr><td>Bond open</td><td>Process this message when the bond state is Open.</td><td>&#x3C;true></td></tr></tbody></table>

*\*These fields are automatically populated.*

*Your Bond form should look like this:*

![](/files/-Mf3OmdmEVokinvEgrZs)

Navigate to **Inbound > Settings**.

## Inbound Settings Fields

The Inbound Settings fields to be configured are as follows:

<table><thead><tr><th width="176.40414507772022">Field</th><th width="343.33333333333337">Description</th><th width="150">Value</th></tr></thead><tbody><tr><td>Bond reference method*</td><td>Method of searching for and validating an existing bond for incoming messages.</td><td>'External'</td></tr></tbody></table>

{% hint style="info" %}
*\*Bond reference method:*

*Internal -* lookup using the internal reference only.

*External -* lookup using the external reference only.

*Both -* lookup using both the internal and external references.
{% endhint %}

{% hint style="success" %}
We have chosen the 'External' method because, in the payload we built, we only supplied the `source_reference`. If we had also supplied the `correlation_id` as the `target_reference`, then we would have chosen 'Both' *(which would have offered an extra level of validation to the checking)*.
{% endhint %}

*Your Inbound Settings form should look like this:*

![](/files/-Mf3Pnszg8VP2eUb4m1r)

Click **Save**.

We are now ready to configure the **Fields** for our **UpdateIncidentInbound** Message.