> 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/transport/snapshots.md).

# Snapshots

Whenever there is an update to a bonded record, Unifi will take a snapshot of it and capture it in a Snapshot record. The Snapshot is the key to facilitating automated Integration testing.

## Definition

A Snapshot is a representation of the bonded record and data from the relevant message that created/updated it.

A snapshot is created in one of two scenarios:

* A process record is updated and one or more integrations are interested in it (outbound).
* A process record is updated by an integration (inbound).

## Processing

In the Unifi Transport Data Flow process (see the diagram [here](/unifi/3.1/transport/transport-data-flow.md)), the Snapshot record sits between the Stage and the source/target record.  In order for it to be an accurate representation of the source/target record, the Snapshot is taken the same side of the relevant Message Script.

### Outbound

 A snapshot is taken of the source record prior to running the Source to Stage Message Script (before transforming any data).

### Inbound

 A snapshot is taken of the target record after running the Stage to Target Message Script (after transforming any data).

## Fields

Snapshots can be viewed by navigating to **Unifi > Transport > Snapshots**.

The top of the Snapshot record looks like this:

![](https://605238050-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MQBk35gIi557UHt7QlJ%2F-MeACDGCG327L4_lzarF%2F-MeAMWASDQBYs4oLIVKB%2FSnapshot%201.png?alt=media\&token=64f5bdca-a51a-49db-bccc-1436d93149b9)

The bottom of the Snapshot record looks like this:

![](https://605238050-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MQBk35gIi557UHt7QlJ%2F-MeACDGCG327L4_lzarF%2F-MeAMcXRtD_duORTKkys%2FSnapshot%202.png?alt=media\&token=aa6f1cd5-e1fa-4e66-aa4f-4aa271b4f1b3)

The following table gives a description of the fields that are visible on the Snapshot record.

<table><thead><tr><th width="157.08602422061594">Field</th><th width="150">Type</th><th width="417.2163691310651">Description</th></tr></thead><tbody><tr><td>Number</td><td>String</td><td>The system generated unique identifier for this record.</td></tr><tr><td>Direction</td><td>Choice</td><td>The direction of the Snapshot.  Choices: None, Inbound, Outbound</td></tr><tr><td>Table</td><td>Table Name</td><td>The source/target table of the bonded record.</td></tr><tr><td>Document</td><td>Document ID</td><td>The source/target bonded record.</td></tr><tr><td>Messages</td><td>String</td><td>Object containing details of the Message that initiated the Transaction and its Integration.</td></tr><tr><td>Previous</td><td>String</td><td>The JSON representation of the bonded record before any update was made.</td></tr><tr><td>Current</td><td>String</td><td>The JSON representation of the bonded record at the time Unifi was invoked.  Fields may differ to previous values here through form updates, business rules, etc.</td></tr><tr><td>After</td><td>String</td><td>The JSON representation of the bonded record after Unifi processing is complete.</td></tr></tbody></table>