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

|  #  | Field        | Description                                                         | Value                   |
| :-: | ------------ | ------------------------------------------------------------------- | ----------------------- |
|  1  | Message name | The message name that is unique for this integration.               | 'UpdateIncidentInbound' |
|  2  | Type         | The primary purpose of the message.                                 | 'Update'                |
|  3  | Direction    | The direction(s) this message is configured to support.             | 'Inbound'               |
|  4  | Description  | The description for this message and the requirement it is meeting. | \<Your description>     |

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

![](https://796541950-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MQBk35gIi557UHt7QlJ%2F-MR5xbQcj07PoBNlYt4A%2F-MR5yJv4CnCLr3GrbvEP%2FV2%20-%20UpdateIncidentInbound%201.png?alt=media\&token=fd864b79-c7b1-4786-ac5e-b7bd795f4102)

5\) Click **Submit and view** to further configure the Message.

## Response Fields

Navigate to **Message > Response**.

The Response fields to be configured are as follows:

|  #  | Field    | Description                                                                                                                              | Value                 |
| :-: | -------- | ---------------------------------------------------------------------------------------------------------------------------------------- | --------------------- |
|  6  | Response | The immediate synchronous response to this message.                                                                                      | \<lookup: 'Response'> |
| 7\* | Async    | Turn this option on if you want inbound processing to occur asynchronously or this message is the first of an asynchronous message pair. | \<false>              |

*\*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:*

![](https://796541950-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MQBk35gIi557UHt7QlJ%2F-MR5xbQcj07PoBNlYt4A%2F-MR6-0Jm9K0tudyacqNk%2FV2%20-%20UpdateIncidentInbound%202.png?alt=media\&token=7ff42e61-bf62-4bd5-a04d-c863259054fd)

8\) Navigate to **Message > Bond**.

## Bond Fields

The Bond fields to be configured are as follows:

|  #  | Field               | Description                                                                                                                                                                                                 | Value    |
| :-: | ------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- |
|  \* | Bond ownership      | 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.  *(Choices: Ignore, Must own, Must not own.)*           | 'Ignore' |
|  \* | Bond condition type | The type of conditional check made on the bond. (*None:* no checks are made. *State:* checks against the state are made using the conditional checkboxes. *Scripted:* the 'Bond condition' script is used.) | 'State'  |
|  9  | Bond open           | Process this message when the bond state is Open.                                                                                                                                                           | \<true>  |

*\*These fields are automatically populated.*

*Your Bond form should look like this:*

![](https://796541950-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MQBk35gIi557UHt7QlJ%2F-MR5xbQcj07PoBNlYt4A%2F-MR6-AwzE6BJq0-BFq3Y%2FV2%20-%20UpdateIncidentInbound%203.png?alt=media\&token=a52f7b61-70de-4e08-98e9-76b0a703ac9c)

10\) Navigate to **Inbound > Settings**.

## Inbound Settings Fields

The Inbound Settings fields to be configured are as follows:

|  #  | Field                   | Description                                                                    | Value      |
| :-: | ----------------------- | ------------------------------------------------------------------------------ | ---------- |
|  11 | Bond reference method\* | Method of searching for and validating an existing bond for incoming messages. | 'External' |

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

![](https://796541950-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MQBk35gIi557UHt7QlJ%2F-MR5xbQcj07PoBNlYt4A%2F-MR6-eh7oeZSqaKsOoYq%2FV2%20-%20UpdateIncidentInbound%204.png?alt=media\&token=a5064b78-6b5e-4380-af63-5578d613aab3)

12\) Click **Save**.

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