---
title: "Use the record history widget to view changes to table records"
slug: "use-the-record-history-widget-to-view-changes-to-table-records"
updated: 2025-06-26T18:01:14Z
published: 2025-06-26T18:01:14Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.tulip.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Use the record history widget to view changes to table records

*Review record changes in the context of your processes*

          Who can use this feature

          

Users on Regulated plans.

Capturing GxP data and ensuring data integrity is a vital component of app building, and it's important to have visibility into the changes that take place throughout your app.

Tulip's approach to data integrity follows GMP guidelines and the concepts summarized by the acronym, ALCOA:

- **A**ttributable
- **L**egible
- **C**ontemporaneous
- **O**riginal
- **A**ccurate

ALCOA+ builds off the existing acronym to incorporate four additional concepts:

- Complete
- Consistent
- Enduring
- Available

## Digital Record History Overview

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Using%20the%20Record%20History%20Widget%20to%20View%20Changes%20to%20Table%20Records_263335922.png)

The history Widget offers visibility and traceability into the creation, update and deletion of Table Records. It is an interactive, scrollable widget, that you can embed within your app, and link to a specific table record.

![Record History Widget scroll through](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Record%20History%20Widget%20scroll%20through.gif)

This offers the ability to verify, or approve, the change of the table record itself, the state of other variables within the app at the time of completion, and if applicable, the e-signature of the user within the app.

You might find this widget especially powerful for batch work, subassemblies, and material management. From a quality perspective, this widget can be leveraged in the approval process of your batch work.

### Information included in the Record History

The Record History will first show a header that includes the following information:

- Logged-in User
- App name
- Station name
- Step name
- Timestamp

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Using%20the%20Record%20History%20Widget%20to%20View%20Changes%20to%20Table%20Records_263336730.png)

The widget will then include information about the change of the record itself, including:

- Type of edit (Create, Update, Delete etc.)
- Original value
- New Value
- Timestamp

### Additional information

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Using%20the%20Record%20History%20Widget%20to%20View%20Changes%20to%20Table%20Records_263349795.png)

- Logged process data: The values of Variables within your app when the app was completed. Note: These variables must have 'Saved for Analysis' enabled on them.

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Using%20the%20Record%20History%20Widget%20to%20View%20Changes%20to%20Table%20Records_263349906.png)

- Electronic Signature: This will include the verification of signature, the reason for signature and the User associated

[Read more about e-signatures](https://support.tulip.co/docs/creating-a-signature-form-step)

## Embedding the History Widget

First, open the step you'd like to embed your Widget within. Then click Embed, and select Record History.

### History Widget Configuration

![RHW Configuration](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/RHW%20Configuration.png)

- **Linked Placeholder:** Link the Table Record you'd like to show the history for
- **Enable Printing:** When enabled, a print button will display in the header of the Widget
- **Sorting Default:** Option to sort dates from *newest to oldest* or *oldest to newest.*
- **Hide Sorting Options:** A toggle to enable sorting while running the app. If on, the sorting options will be visible to the user.
- **Filters:** Filter the record history, similar to filtering of [Embedded Tables](https://support.tulip.co/docs/displaying-interactive-lists-of-table-records-or-connector-output-in-apps) The following filters are available:

|  |  |
| --- | --- |
| Filter | Description |
| Datetime | The date and time an event occurred |
| App Name | The name of the app where data was modified. |
| Step Name | The step within an app where data was modified. |
| Table Field Name | The name of the field from Tulip Tables that was modified. |
| User | The person who made the changes. |
| All Fields from *Linked Placeholder* | The values of all fields in the history can be used in filters. For example, *Density > X*. This could be useful in finding changes that are outside a certain standard. |

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Using%20the%20Record%20History%20Widget%20to%20View%20Changes%20to%20Table%20Records_320217374.png)

- **Hide "Old" Values in Record Updates:** This will hide the previous value for all fields and only the current value will be shown. Useful for making the history more compact when necessary.
- **Hide Process Data:** Hide all blocks within the Record History that pertain to *Process Data*. Useful when all critical data is being captured in a Tulip Table.
- **Signed Completions Only:** When on, only blocks of data within the history that contain signatures will be shown. Helpful to quickly narrow down the history to milestone events.

## Further Reading

- [A Summary of Tulip's GxP Capabilities](https://support.tulip.co/docs/a-summary-of-tulips-gxp-capabilities)

---

Did you find what you were looking for?

You can also head to [community.tulip.co](https://community.tulip.co/?utm_source=intercom&utm_medium=article-link&utm_campaign=all) to post your question or see if others have faced a similar question!

**GxP**

**Good *X* Practice**. An abbreviation collecting many of the core principles of Life Sciences compliance.

*ex-*

- *GMP - Good Manufacturing Practice*
- *GLP - Good Laboratory Practice*
- *GDP - Good Distribution Practice*

**Digital Record History Widget**

The **DRH Widget**allows users to review the changes that have occurred to a **Record.**Traceability to changes is critical in a **GxP**Environment.

**Widget**

**Widgets**are the elements that make up a specific **App Step.**Widgets can display information to users, collect user input, or trigger app logic.

*Common widgets include: Interactive Tables, Number inputs, Machine attribute widgets, and more.*

**Table Record**

A **Table Record** is a reference to a row in a **Tulip Table**. Table Records can be created either from the Table UI or from with an App Trigger.

To edit a record it must be loaded into a **Table Record Placeholder.**

**Station**

**Stations**are a digital representation of a physical place or device in your facility. Stations are 1:1 with **Interfaces (display devices)** running Tulip Player, but Stations can also be assigned **Edge Devices,**Tulip Vision Camera Configurations, Machines,****and more.

**Step**

A view your users will see within an application. **Steps** can be viewed chronologically or in whatever order best fits your process.

Steps can be grouped into **Step Groups**to manage and organize your app Steps.

**Variables**

**Variables**are a location to store app information. Variables have a specific type that must match the contents they can store.

Variables are only accessible within a single application and are cleared when the app is restarted or completed.

**Electronic Signatures**

In regulated environments (GxP) getting a user signature to the accuracy of data is critical for process validation. The **E-Sig Widget**allows users to collect user signatures along with associated metadata.

**Linked Placeholder**

**Linked Placeholder**are one of the**Side Pane**settings for the Interactive Table **Widget**and **Record** **History** Widget**.**This setting can be tied to a **Table Record Placeholder,**and when users select a row in the **Widget,**that record is loaded into the mapped **Record Placeholder.**