--- title: "Checkpoint Component" slug: "checkpoint-component" updated: 2025-12-04T19:33:59Z published: 2025-12-04T19:33:59Z canonical: "docs.unqork.io/checkpoint-component" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.unqork.io/llms.txt > Use this file to discover all available pages before exploring further. # Checkpoint Component UDesignerClassic Designer The **Checkpoint component** is a Centauri (v1.0) component that helps you track an end-user's location in an [application](/v1/docs/introduction-to-unqork-applications). You can place Checkpoint components throughout your application. When end-users reach a checkpoint, the [component](/v1/docs/module-builder-component-library) records a timestamp. You can use this timestamp data in many ways, including: - Creating a [dashboard](/v1/docs/dashboard-configurations) that displays crucial "drop-off" points in your application. - Integrating with client data to notify end-users to complete their unfinished work. For the Checkpoint component to work, you need to trigger it. The easiest way to trigger a Checkpoint component is using an [Initializer](/v1/docs/initializer-component) component. There's no visual aspect of a Checkpoint component in Express View. When a Checkpoint component executes, it creates an entry in the [submission data](/v1/docs/submission-data). You can retrieve this data using `metadata.checkpoints.<checkpointPropertyID>` and view its timestamp in Unix time. [![A static image displaying the checkpoint metadata in the DevTools Console.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/AppBuild_Checkpoint_05_thumb_0_0.jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A40Z&se=2026-11-07T18%3A57%3A40Z&sr=c&sp=r&sig=VR0Cx%2BnpV0NrdBMZohUFkz5LR54fCBxF1SpAkZz7SWU%3D)](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/AppBuild%20Checkpoint%2005.jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A40Z&se=2026-11-07T18%3A57%3A40Z&sr=c&sp=r&sig=VR0Cx%2BnpV0NrdBMZohUFkz5LR54fCBxF1SpAkZz7SWU%3D) You'll find the Checkpoint component under the [Data & Event Processing](/v1/docs/data-event-processing-components) group to the left of the [Module Builder](/v1/docs/introduction-to-the-module-builder). ## About the Configuration Window > To learn more about general component settings, view our [General Component Settings](/v1/docs/general-component-settings) article. ## Display Setting ### Field Text | **Setting** | Description | | --- | --- | | **Label Text** | Label Text conveys what the input component is and what information it displays. Enter the purpose of the corresponding component or field. User-friendly labels make your module more accessible. Keep labels short and descriptive (a word or two) using title case. For longer entries, use sentence case. | ## [![A static image displaying the Disply Settings of Checkpoint Component.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/display_thumb_0_0(16).jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A40Z&se=2026-11-07T18%3A57%3A40Z&sr=c&sp=r&sig=VR0Cx%2BnpV0NrdBMZohUFkz5LR54fCBxF1SpAkZz7SWU%3D)](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/display(18).jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A40Z&se=2026-11-07T18%3A57%3A40Z&sr=c&sp=r&sig=VR0Cx%2BnpV0NrdBMZohUFkz5LR54fCBxF1SpAkZz7SWU%3D) Data Setting ### User Input | **Setting** | Description | | --- | --- | | **Allow Checkpoint to Be Set Multiple Times** | When set to ![A toggle switch indicating an on/off state for a user interface element.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Group 1.png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A40Z&se=2026-11-07T18%3A57%3A40Z&sr=c&sp=r&sig=VR0Cx%2BnpV0NrdBMZohUFkz5LR54fCBxF1SpAkZz7SWU%3D) **(ON)**, the end-user triggers the Checkpoint component every time they reach a set point in the application. The end-user can also trigger the checkpoint by going backward in the application and then returning to the Checkpoint component's location. When set to ![A toggle switch in the 'on' position, indicating an active setting or feature.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Group 2(1).png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A40Z&se=2026-11-07T18%3A57%3A40Z&sr=c&sp=r&sig=VR0Cx%2BnpV0NrdBMZohUFkz5LR54fCBxF1SpAkZz7SWU%3D) **(OFF)**, the Checkpoint component only records the first time an end-user reaches the checkpoint. By default, this setting is set to ![A toggle switch in the 'on' position, indicating an active setting or feature.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Group 2(1).png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A40Z&se=2026-11-07T18%3A57%3A40Z&sr=c&sp=r&sig=VR0Cx%2BnpV0NrdBMZohUFkz5LR54fCBxF1SpAkZz7SWU%3D) **(OFF)**. | ## [![A static image displaying the Data Setting of Checkpoint Component.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/data_thumb_0_0(10).jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A40Z&se=2026-11-07T18%3A57%3A40Z&sr=c&sp=r&sig=VR0Cx%2BnpV0NrdBMZohUFkz5LR54fCBxF1SpAkZz7SWU%3D)](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/data(12).jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A40Z&se=2026-11-07T18%3A57%3A40Z&sr=c&sp=r&sig=VR0Cx%2BnpV0NrdBMZohUFkz5LR54fCBxF1SpAkZz7SWU%3D) Adding a Checkpoint Component Configure a Checkpoint component to executes when your end-user applies a signature with a [Signature](/v1/docs/signature-component) component. You'll use an [Initializer](/v1/docs/initializer-component) component to trigger the Checkpoint component. ### Configure the Signature Component First, configure a Signature component so your end-user can apply a signature. 1. In the Module Builder, drag and drop a **S****ignature** component onto your canvas. 2. In the Property ID field, enter **signature**. 3. Click **Save Component**. ### Configure the Checkpoint Component Next, configure the Checkpoint component to retrieve a timestamp when the end-user applies a signature. 1. Drag and drop a **Checkpoint** component onto your canvas, placing it below the **signature** **S****ignature** component. 2. In the Property ID field, enter **cpSignature**. 3. In the Canvas Label Text field, enter `Checkpoint`. 4. Click **Save Component**. ### Configure the Initializer Component Lastly, configure an Initializer component to trigger the Checkpoint component. 1. Drag and drop an **I****nitializer** component onto your canvas, placing it between the **signature** **S****ignature** and **cpSignature** **Checkpoint** components. 2. 2.In the Property ID field, enter **initCheckpoint**. 3. In the Canvas Label Text field, enter initCheckpoint. 4. Set the Trigger Type to **Watch**. 5. In the Inputs table, enter the following: | | Property ID | Alias | Required | | --- | --- | --- | --- | | 1 | signature | | (**checked**) | 6. In the Outputs table, enter the following: | | Property ID | Type | Value | | --- | --- | --- | --- | | 1 | cpSignature | trigger | GO | 7. Click **Save Component**. 8. **Save** your module. ### Viewing the Checkpoint Metadata Now, look at the DevTools Console to see how the Checkpoint component works. To open the DevTools Console tab: 1. Preview your module in Express View. 2. 2.Right-click anywhere on your Express View page. 3. Click **Inspect**. By default, the DevTools panel opens on the right side of your page. > [!TIP] > To open the Console in Google Chrome, you can use the **Ctrl + Shift + J** (Windows/Linux) or **Option + Command + J** (Mac OS) shortcut. 4. At the top of the DevTools panel, click the **Console** tab. The Console tab lets you view your Unqork application's submission data. A blue arrow to the left of a blank row at the bottom of the Console's feed indicates the Console's command line. You'll use this field to enter commands to get more data details. With the DevTools Console open, test out the Checkpoint component. 1. In the **Signature** field, sign your name. 2. Returning to the **Console** tab, enter the following Angular command in the Console's command line: angular.element('.unqorkio-form').scope().submission. 3. Press **Enter**/**Return**. The submission object appears. 4. Click the gray arrows to expand and inspect the submission object until you find the metadata object. The metadata object is where the checkpoint data lives. Expanding the metadata object, you'll see an object called checkpoints. Inside is the timestamp recorded when you signed your name in the **cpSignature** **Checkpoint** component. [![A static image displaying the added signature in Express View and the checkpoint metadata object in the DevTools Console.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/AppBuild_Checkpoint_04_thumb_0_0.jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A40Z&se=2026-11-07T18%3A57%3A40Z&sr=c&sp=r&sig=VR0Cx%2BnpV0NrdBMZohUFkz5LR54fCBxF1SpAkZz7SWU%3D)](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/AppBuild%20Checkpoint%2004.jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A40Z&se=2026-11-07T18%3A57%3A40Z&sr=c&sp=r&sig=VR0Cx%2BnpV0NrdBMZohUFkz5LR54fCBxF1SpAkZz7SWU%3D) As you see in this example, the value is a Unix timestamp of 1679944694537. Converted to a readable date, this value is `GMT Monday, March 27, 2023 7:18:14.537 PM`. The **Checkpoint component** is a Centauri (v1.0) component that helps you track an end-user's location in an [application](/v1/docs/introduction-to-unqork-applications). You can place Checkpoint components throughout your application. When end-users reach a checkpoint, the [component](/v1/docs/module-builder-component-library) records a timestamp. You can use this timestamp data in many ways, including: - Creating a [dashboard](/v1/docs/dashboard-configurations) that displays crucial "drop-off" points in your application. - Integrating with client data to notify end-users to complete their unfinished work. For the Checkpoint component to work, you need to trigger it. The easiest way to trigger a Checkpoint component is with an [Initializer](/v1/docs/initializer-component) component. There's no visual aspect of a Checkpoint component. When a Checkpoint component fires, it creates an entry in the [submission data](/v1/docs/submission-data). You can retrieve this data using metadata.checkpoints. and view its timestamp in Unix time. [![A static image displaying the checkpoint metadata in the DevTools Console.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/AppBuild_Checkpoint_05_thumb_0_0.jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A40Z&se=2026-11-07T18%3A57%3A40Z&sr=c&sp=r&sig=VR0Cx%2BnpV0NrdBMZohUFkz5LR54fCBxF1SpAkZz7SWU%3D)](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/AppBuild%20Checkpoint%2005.jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A40Z&se=2026-11-07T18%3A57%3A40Z&sr=c&sp=r&sig=VR0Cx%2BnpV0NrdBMZohUFkz5LR54fCBxF1SpAkZz7SWU%3D) You'll find the Checkpoint component under the [Data & Event Processing](/v1/docs/data-event-processing-components) group to the left of the [Module Builder](/v1/docs/introduction-to-the-module-builder). ## About the Configuration Window > To learn more about general component settings, view our [General Component Settings](/v1/docs/general-component-settings) article. ## Display Panel [![A static image dispaying the Checkpoint component's Display settings.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Checkpoint_Display_thumb_0_0.jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A40Z&se=2026-11-07T18%3A57%3A40Z&sr=c&sp=r&sig=VR0Cx%2BnpV0NrdBMZohUFkz5LR54fCBxF1SpAkZz7SWU%3D)](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Checkpoint%20Display.jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A40Z&se=2026-11-07T18%3A57%3A40Z&sr=c&sp=r&sig=VR0Cx%2BnpV0NrdBMZohUFkz5LR54fCBxF1SpAkZz7SWU%3D) ### Field Text | Setting | Description | | --- | --- | | Label Text | Label Text conveys what the input component is and what information it displays. Enter the purpose of the corresponding component or field. User-friendly labels make your module more accessible. Keep labels short and descriptive (a word or two) using title case. For longer entries, use sentence case. | ## Data Panel [![A static image dispaying the Checkpoint component's Data settings.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Checkpoint_Data_thumb_0_0.jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A40Z&se=2026-11-07T18%3A57%3A40Z&sr=c&sp=r&sig=VR0Cx%2BnpV0NrdBMZohUFkz5LR54fCBxF1SpAkZz7SWU%3D)](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Checkpoint%20Data.jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A40Z&se=2026-11-07T18%3A57%3A40Z&sr=c&sp=r&sig=VR0Cx%2BnpV0NrdBMZohUFkz5LR54fCBxF1SpAkZz7SWU%3D) ### User Input | Setting | Description | | --- | --- | | Allow Checkpoint to Be Set Multiple Times | When set to ![A toggle switch indicating an on/off state for a user interface element.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Group 1.png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A40Z&se=2026-11-07T18%3A57%3A40Z&sr=c&sp=r&sig=VR0Cx%2BnpV0NrdBMZohUFkz5LR54fCBxF1SpAkZz7SWU%3D) **(ON)**, the end-user triggers the Checkpoint component every time they reach a set point in the application. The end-user can also trigger the checkpoint by going backward in the application and then returning to the Checkpoint component's location. When set to ![A toggle switch in the 'on' position, indicating an active setting or feature.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Group 2(1).png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A40Z&se=2026-11-07T18%3A57%3A40Z&sr=c&sp=r&sig=VR0Cx%2BnpV0NrdBMZohUFkz5LR54fCBxF1SpAkZz7SWU%3D) **(OFF)**, the Checkpoint component only records the first time an end-user reaches the checkpoint. By default, this setting is set to ![A toggle switch in the 'on' position, indicating an active setting or feature.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Group 2(1).png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A40Z&se=2026-11-07T18%3A57%3A40Z&sr=c&sp=r&sig=VR0Cx%2BnpV0NrdBMZohUFkz5LR54fCBxF1SpAkZz7SWU%3D) **(OFF)**. | ## Adding a Checkpoint Component Configure a Checkpoint component to fire when your end-user applies a signature with a [Signature](/v1/docs/signature-component) component. You'll use an [Initializer](/v1/docs/initializer-component) component to trigger the Checkpoint component. ### Configure the Signature Component First, configure a Signature component so your end-user can apply a signature. 1. In the Module Builder, drag and drop a **S****ignature** component onto your canvas. 2. In the Property ID field, enter **signature**. 3. Click **Save & Close**. ### Configure the Checkpoint Component Next, configure the Checkpoint component to retrieve a timestamp when the end-user applies a signature. 1. Drag and drop a **Checkpoint** component onto your canvas, placing it below the **S****ignature** component. 2. In the Property ID field, enter **cpSignature**. 3. In the Label Text field, enter `Checkpoint`. 4. Click **Save & Close**. ### Configure the Initializer Component Lastly, configure an Initializer component to trigger the Checkpoint component. 1. Drag and drop an **I****nitializer** component onto your canvas, placing it between the **signature** **S****ignature** and **cpSignature** **Checkpoint** components. 2. In the Property ID and Canvas Label Text fields, enter **initCheckpoint**. 3. Set the Trigger Type to **Watch**. 4. In the **Inputs** table, enter the following: | Property ID | Alias | Required | | --- | --- | --- | | signature | | (**checked**) | 5. In the **Outputs** table, enter the following: | Property ID | Type | Value | | --- | --- | --- | | cpSignature | trigger | GO | 6. Click **Save & Close**. 7. **Save** your module. ### Viewing the Checkpoint Metadata Now, look at the DevTools Console to see how the Checkpoint component works. To open the DevTools Console tab: 1. Preview your module in Express View. 2. 2.Right-click anywhere on your Express View page. 3. Click **Inspect**. By default, the DevTools panel opens on the right side of your page. > [!TIP] > To open the Console in Google Chrome, you can use the **Ctrl + Shift + J** (Windows/Linux) or **Option + Command + J** (Mac OS) shortcut. 4. At the top of the DevTools panel, click the **Console** tab. The Console tab lets you view your Unqork application's submission data. A blue arrow to the left of a blank row at the bottom of the Console's feed indicates the Console's command line. You'll use this field to enter commands to get more data details. With the DevTools Console open, test out the Checkpoint component. 1. In the **Signature** field, sign your name. 2. Returning to the **Console** tab, enter the following Angular command in the Console's command line: angular.element('.unqorkio-form').scope().submission. 3. Press **Enter**/**Return**. The submission object appears. 4. Click the gray arrows to expand and inspect the submission object until you find the metadata object. The metadata object is where the checkpoint data lives. Expanding the metadata object, you'll see an object called checkpoints. Inside is the timestamp recorded when you signed your name in the **cpSignature** **Checkpoint** component. [![A static image displaying the added signature in Express View and the checkpoint metadata object in the DevTools Console.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/AppBuild_Checkpoint_04_thumb_0_0.jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A40Z&se=2026-11-07T18%3A57%3A40Z&sr=c&sp=r&sig=VR0Cx%2BnpV0NrdBMZohUFkz5LR54fCBxF1SpAkZz7SWU%3D)](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/AppBuild%20Checkpoint%2004.jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A40Z&se=2026-11-07T18%3A57%3A40Z&sr=c&sp=r&sig=VR0Cx%2BnpV0NrdBMZohUFkz5LR54fCBxF1SpAkZz7SWU%3D) As you see in this example, the value is a Unix timestamp of 1679944694537. Converted to a readable date, this value is `GMT Monday, March 27, 2023 7:18:14.537 PM`. ## Resources - [Modify the Checkpoint component using the toolbar settings](/v1/docs/component-toolbar-settings). - [Initializer Component](/v1/docs/initializer-component) - [Signature Component](/v1/docs/signature-component) The Centauri (v 1.0.0) runtime is the first-generation foundation of the Unqork Designer Platform. Centauri provides Creators a codeless experience for developing applications. End-users, also known as Express Users, are the individuals accessing an application through Express View. In most cases, end-users are the customers using the product. End-users, also known as Express Users, are the individuals accessing an application through Express View. In most cases, end-users are the customers using the product. Express View is how your end-user views your application. Express View also lets you preview your applications to test your configuration and view the styling. This is also the view your end-users will see when interacting with your application. After configuring a module, click Preview in the Module Builder to interact with the module in Express View. Unix time is measured by the number of seconds elapsed since 00:00:00 UTC on 1 January 1970, the beginning of the Unix epoch. Triggers activate another component when certain requirements are met. Trigger types include Concurrent, Post, and Error. Some components do not have the ability to trigger others. A Property ID is the unique field ID used by Unqork to track and link components in your module. Canvas Label Text indicates the purpose of the corresponding field or component. For non-input components, the Canvas Label Text isn't end-user facing, and only appears in the . Deteremines how the component triggers. Enter inputs components and actions you want the component to perform. Enter outputs components and actions you want the component to perform. The DevTools Console helps you securely store, build, test, and deploy your software. Also known as Record Data. Submission data consists of information saved by Unqork components. View submission data by using the angular command, or in Record Collections. Label Text conveys what the input component is and what information it displays. Enter the purpose of the corresponding component or field.