# ResolveIncident Message

*Again, after clicking the **'Messages' icon**, you are directed to the following screen (note: the four previously configured messages are now visible in the list):*

![](https://2404534899-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MQBk35gIi557UHt7QlJ%2F-MexulylZ7T19Ve-vcOG%2F-Mey_uYn3QdrhBxsh74P%2FOBIG%20-%20ResolveIncident%201.png?alt=media\&token=7ddaefb2-8a55-4498-9350-0f4bdf68fac1)

1\) Click the **ellipsis** to the right of the **UpdateIncident** Message & then click **Copy**.

{% hint style="success" %}
It is now easier than ever to create the ResolveIncident Message. Rather than create it from scratch, it will be quicker to copy the UpdateIncident Message and make some minor changes.
{% endhint %}

## Copy Message Modal

The fields to edit for the Copy Message modal are as follows:

|  #  | Field        | Description                                           | Value             |
| :-: | ------------ | ----------------------------------------------------- | ----------------- |
|  2  | Message name | The message name that is unique for this integration. | 'ResolveIncident' |

*Your Copy Message modal should look like this:*

![](https://2404534899-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MQBk35gIi557UHt7QlJ%2F-MexulylZ7T19Ve-vcOG%2F-MeyalOi9Qy7V08W3-ym%2FOBIG%20-%20ResolveIncident%202.png?alt=media\&token=1843ae9a-5237-4c72-aa3b-476a760602e0)

3\) Click **Copy**.

You will be redirected to the Details page of the newly created ResolveIncident Message.

## Bond Fields

Navigate to **Message > Bond**.

The Bond fields to be edited are as follows:

|  #  | Field                 | Description                                                                      | Value   |
| :-: | --------------------- | -------------------------------------------------------------------------------- | ------- |
|  4  | Bond suspended        | Process this message when the bond state is Suspended (internal suspend).        | \<true> |
|  5  | Bond vendor suspended | Process this message when the bond state is Vendor suspended (external suspend). | \<true> |

*Your Bond form should look like this:*

![](https://2404534899-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MQBk35gIi557UHt7QlJ%2F-MexulylZ7T19Ve-vcOG%2F-MeycrMXVSG1BAEtVcAf%2FOBIG%20-%20ResolveIncident%203.png?alt=media\&token=c28022e3-bbac-4330-a4ed-52551e3f1b1d)

6\) Navigate to **Outbound > Trigger**.

## Outbound Trigger Fields

The Outbound Trigger *(as required)*\* fields to be edited are as follows:

|  #  | Field                       | Description                                                                                 | Value                           |
| :-: | --------------------------- | ------------------------------------------------------------------------------------------- | ------------------------------- |
|  7  | Outbound conditio&#x6E;*\** | The condition that the ServiceNow record must meet to trigger this message being processed. | 'State > changes to > Resolved' |

{% hint style="info" %}
*\*Outbound condition (as required):*

*It is not necessary for you to enter a condition. The value given is an example. You may create any condition (or not) to align with your business process requirements.  In this case, it makes sense to send the ResolveIncident Message when the state changes to Resolved.*
{% endhint %}

*Your Outbound Trigger form should look like this:*

![](https://2404534899-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MQBk35gIi557UHt7QlJ%2F-MexulylZ7T19Ve-vcOG%2F-Meydoknw2AOo2oIOZY8%2FOBIG%20-%20ResolveIncident%204.png?alt=media\&token=0b86640f-be1e-46fc-9c89-28dfd68c9644)

8\) Click **Save**.

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