> 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/bidirectional-asynchronous-incident-guide/create-scenario/createincidentreceipt-fields.md).

# CreateIncidentReceipt Fields

## Copy Field Maps

{% hint style="info" %}
It is worth copying all relevant OOTB Field Maps as are necessary for your integration before using any of them in your Field Records - thereby mitigating the risk of any potential issues with future upgrades.
{% endhint %}

The Field Maps we shall use for our CreateIncidentReceipt Field records are:

* Message Header
* Receipt Status

To copy the Message Header Field Map, navigate to the **'Field Maps' icon**.

![](/files/-MdaPODp9ZT5XeOsS7c1)

Click on the **ellipsis** to the right of the **Message Header** Field Map & then click **Copy**.

## Copy Field Map Modal

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

<table><thead><tr><th width="194.33333333333331">Field</th><th width="319.71060011217054">Description</th><th>Value</th></tr></thead><tbody><tr><td>Name</td><td>The name of your field map. (If left unedited, it will append the word 'Copy' to the existing name.)</td><td>&#x3C;Your Name></td></tr><tr><td>Integration*</td><td>The integration this field map is associated with.</td><td>&#x3C;Your Integration></td></tr></tbody></table>

*\*This field is automatically populated.*

{% hint style="success" %}
*Name: We have chosen to prefix the existing Field Map Name with the initials of our Integration (you are free to choose any appropriate means of identifying/differentiating).*
{% endhint %}

*Your Copy Field Map modal should look like this:*

![](/files/-MdaQSHiYQSzeRdLM-Pq)

Click **Copy**.

You will be redirected to the Details page of the newly created Field Map.

{% hint style="success" %}
**Repeat** the process for the **Receipt Status** Field Map.
{% endhint %}

## Field: message.message\_header

From the **CreateIncidentReceipt** Message, navigate to **Message > Fields**. Click **New**.

![](/files/-MdaMoHYYY8iGTlXxd5X)

The fields to be configured for our message\_header New Field modal are as follows:

<table><thead><tr><th width="190.33333333333331">Field</th><th width="316.416149068323">Description</th><th>Value</th></tr></thead><tbody><tr><td>Message*</td><td>The Message this Field record is linked with.</td><td>'CreateIncidentReceipt'</td></tr><tr><td>Description</td><td>Describe what this field is for and any specific details that might help you in future.</td><td>'The protocol message header'</td></tr><tr><td>Active*</td><td>Set to true to use this Field record for processing.</td><td>&#x3C;true></td></tr><tr><td>Field map</td><td>The Field Map this Field record is linked with.</td><td>'IG - Message Header'**</td></tr><tr><td>Map to field*</td><td>Use this Field record to represent a field on a source/target table.</td><td>&#x3C;false></td></tr><tr><td>Path</td><td>Where in the payload the data will be placed.</td><td>'message'</td></tr><tr><td>Property</td><td>The property in the payload the data will be written to.</td><td>'message_header'</td></tr><tr><td>Inbound*</td><td>Set to true to use for inbound Messages.</td><td>&#x3C;true></td></tr><tr><td>Outbound*</td><td>Set to true to use for outbound Messages.</td><td>&#x3C;true></td></tr></tbody></table>

*\*These fields are automatically defaulted to true, or automatically populated.*

*\*\*Field map: Value may vary. Choose the copy Field Map you created for your Integration.*

*Your 'message\_header' New Field modal should look like this:*

![](/files/-MdaSJT8cadFfJ7N3m4S)

**Submit** the record.

You will be redirected back to the Fields page of the CreateIncidentReceipt Message.

## Field: message.transaction\_details

Click **New**.

The fields to be configured for our transaction\_details New Field modal are as follows:

<table><thead><tr><th width="179.33333333333331">Field</th><th width="297.22784810126586">Description</th><th>Value</th></tr></thead><tbody><tr><td>Message*</td><td>The Message this Field record is linked with.</td><td>'CreateIncidentReceipt'</td></tr><tr><td>Description</td><td>Describe what this field is for and any specific details that might help you in future.</td><td>'Used to send and receive transaction process errors'</td></tr><tr><td>Active*</td><td>Set to true to use this Field record for processing.</td><td>&#x3C;true></td></tr><tr><td>Field map</td><td>The Field Map this Field record is linked with.</td><td>'IG - Receipt Status'**</td></tr><tr><td>Map to field*</td><td>Use this Field record to represent a field on a source/target table.</td><td>&#x3C;false></td></tr><tr><td>Path</td><td>Where in the payload the data will be placed.</td><td>'message'</td></tr><tr><td>Property</td><td>The property in the payload the data will be written to.</td><td>'transaction_details'</td></tr><tr><td>Inbound*</td><td>Set to true to use for inbound Messages.</td><td>&#x3C;true></td></tr><tr><td>Outbound*</td><td>Set to true to use for outbound Messages.</td><td>&#x3C;true></td></tr></tbody></table>

*\*These fields are automatically defaulted to true, or automatically populated.*

*\*\*Field map: Value may vary. Choose the copy Field Map you created for your Integration.*

*Your 'transaction\_details' New Field modal should look like this:*

![](/files/-MdaVRK8zeVTXn2GAvQX)

**Submit** the record.

You will be redirected back to the Fields page of the CreateIncidentReceipt Message.

## Build

Now that we’ve configured the Field records for the CreateIncidentReceipt message, we are ready to build our message scripts.

*The following Field records should now be in place for your CreateIncidentReceipt messsage:*

![](/files/-MdaY8oNLefcK3VRJlFs)

{% hint style="success" %}
**Feature Alert**: In the picture above you will notice that a 'Build Integration' button has appeared in the banner at the top of the page. Whenever a change is made to a Field record that is associated to a Message *(whether that is being created, updated, or deleted)* the button will be available and acts as a visual reminder that changes have been made and Message Script(s) need to be built. We will talk more about this feature in the [Build Integration Level](/unifi/3.1/integration-guides/bidirectional-asynchronous-incident-guide/build-integration-level.md) page.
{% endhint %}

Navigate to **Advanced > Script Editor**.

*When you first open the Script Editor, you will see the following:*

![](/files/-MdaYrDYreUO9oBKjH9s)

{% hint style="success" %}
Having visibility of your message scripts in the one pane makes scripting so much more efficient.
{% endhint %}

Click on **Build Message**.

You will see the 'Message build successful' Info Message.

![](/files/-MR-q0v-I-k77qv4tvEf)

*Your Script Editor fields should now look like this:*

![](/files/-MdacNrDd94BWaUJ_S_7)

You can click **View** to adjust the layout and change the view to show various combinations of, or individual script fields.

![](/files/-MdadYBZNaRYdP7Sl7H4)

## Message Scripts

{% hint style="info" %}
The newly auto-generated code will appear between a Begin & End Comment immediately prior to any code that may already be there (pre-existing code will be retained).
{% endhint %}

```javascript
//===== [ws] Begin Unifi Auto Generated Code =====//

/*
 * This code (between the Begin and End comments) is generated from the
 * Field and Field mapping records which are configured as part of the integration.
 *
 * All code either above or below the comments will be automatically maintained
 * through the build cycle.
 *
 * WARNING: Do not edit the Begin or End comments.
 */

(New auto-generated code will appear here)

//===== [ws] End Unifi Auto Generated Code =====//

(Old pre-existing code will appear here)
```

&#x20;Once you have finished examining the code, click **'Close'** to navigate back to the Fields page of the CreateIncidentReceipt Message.

![](/files/-Mdalki7UfUsb0_i53Si)

We are now ready to configure our **CreateIncident** Message.