---
title: "How to: Display a Delete Button in a Simple Dashboard"
slug: "use-case-showing-a-delete-button-in-a-simple-dashboard"
updated: 2026-02-03T15:37:07Z
published: 2026-02-03T15:48:58Z
canonical: "docs.unqork.io/use-case-showing-a-delete-button-in-a-simple-dashboard"
---

> ## 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.

# How to: Display a Delete Button in a Simple Dashboard

**UDesigner**

Many dashboards require multiple buttons to perform various actions. For example, one to view a submission and one to delete it.

In this how-to guide, you'll learn how to **display a Delete button in a dashboard**.

> [!TIP]
> This example includes steps for building a simple dashboard. The dashboard retrieves submissions from the following source module: [https://trainingx.unqork.io/#/display/5eb01aa6811bf80215fd706b](https://trainingx.unqork.io/#/display/5eb01aa6811bf80215fd706b).

## Preconfiguration

Begin by setting up basic components for this example.

### Configure the Panel Component

This [Panel](/v1/docs/panel-component) component acts as a container for the components that follow.

1. In the Module Builder, drag and drop a **Panel** component onto the canvas.
2. In the **Property ID** field, enter `panelDashboard`.
3. Click **Save Component**.

### Configure the Initializer Component

Next, add an [Initializer](/v1/docs/initializer-component) component to trigger a [Plug-In](/v1/docs/plug-in-component) component that you'll set up next.

1. Drag and drop an **Initializer** component inside the `panelDashboard` **Panel** component.
2. In the **Property ID** and **Canvas** **Label Text** fields, enter `initStart`.
3. From the **Trigger Type** drop-down, select **New Submission**.
4. In the **Outputs** table, enter the following:

| # | Source | Type | Value |
| --- | --- | --- | --- |
| 1 | pluginGetSubmissions | trigger | GO |

> [!NOTE]
> You’ll configure the `pluginGetSubmissions` **Plug-In** component in the next steps.
5. Click **Save Component.**

### Configure the First Hidden Component

Now, let's add a [Hidden](/v1/docs/hidden-component) component to store the module ID of your source or submission module.

1. Drag and drop a **Hidden** component inside the `panelDashboard` **Panel** component, below the Initializer component.
2. In the **Property ID** and **Label Text** fields**,** enter `moduleId`.
3. In the **Default Value** field, enter `5eb01aa6811bf80215fd706b`.

> [!NOTE]
> This module ID is taken from the source module: https://training.unqork.io/#/form/**5eb01aa6811bf80215fd706b**/edit.
4. Click **Save Component**.

### Configure the Plug-In Component

This [Plug-In](/v1/docs/plug-in-component) component connects the module to the external systems using an API. You’ll use this component to retrieve submissions and display them in your dashboard.

1. Drag and drop a **Plug-In** component inside the `panelDashboard` **Panel** component, below the Hidden component.
2. In the **Property ID** and **Canvas Label Text** fields, enter `pluginGetSubmissions`.
3. From the **Internal Services** drop-down, select **List Submissions for Dashboard.** The **Data Source URL** field autopopulates.
4. In the **Inputs** table, enter the following:

| # | Property ID | Mapping |
| --- | --- | --- |
| 1 | moduleId | moduleId |
| 2 | 'firstName,middleName,lastName,email,dateOfBirth' | fields |

> [!NOTE]
> The first row reference the module ID stored in the `moduleId` **Hidden** component. The second row represents the fields that populate the dashboard. The values entered in the Mapping column (`moduleId` and `fields`) are native values recognized by the Unqork platform.
5. Click **Save Component.**

### Configure the Second Hidden Component

This [Hidden](/v1/docs/hidden-component) component stores the submission ID.

1. Drag and drop a **Hidden** component inside the `panelDashboard` **Panel** component, below the Plug-In component.
2. In the **Property ID** and **Label Text** fields**,** enter `submissionId`.
3. Set **Store Data in Database** to ![files](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/toggle_ON(15).png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A57Z&se=2026-11-07T18%3A57%3A57Z&sr=c&sp=r&sig=oV4yl9PrK%2FsPQn%2BRKcVEEhYDWlyCsn%2FP2gneqtOigQI%3D) **(****ON)**.
4. Click **Save Component**.

### Configure the ViewGrid Component

Next, add a [ViewGrid](/v1/docs/viewgrid-component) component to display your dashboard. Notice how the **Action** and **Event** settings create the **View** button.

1. Drag and drop a **ViewGrid** component inside the `panelDashboard` **Panel** component, below the `submissionId` **Hidden** component.
2. In the **Property Id** field, enter `gridView`.
3. In the **Canvas** **Label Text** field, enter `View Grid`**.**
4. In the **Inputs** table, enter the following:

| # | Source | Required |
| --- | --- | --- |
| 1 | pluginGetSubmissions | Yes (required) |
5. In the **Outputs** table, enter the following:

| # | Source | Mapping |
| --- | --- | --- |
| 1 | submissionId | Id |
6. In the **Display** table, enter the following:

| # | ID | Formula | Heading |
| --- | --- | --- | --- |
| 1 | firstName |  | First Name |
| 2 | middleName |  | Middle Name |
| 3 | lastName |  | Last Name |
| 4 | email |  | Email |
| 5 | dateOfBirth | =MOMENT(MOMENT(dateOfBirth), 'format','MM/DD/YY') | Date of Birth |

> [!NOTE]
> The Moment.js in the Formula column formats the `dateOfBirth` values as MM/DD/YY.
7. In the **Action** and **Event** fields, enter `View`.
8. Click **Save Component**.

## Configuration

Next, you’ll add the second action button by updating the [ViewGrid](/v1/docs/component-library-viewgrid-component) component and configuring a new [Plug-In](/v1/docs/plug-in-component) and [Decisions](/v1/docs/decisions-component) component.

### Update the ViewGrid Component

1. Hover over the `gridView` **ViewGrid** component and click the ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/AppBuildButton_Settings(45).jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A57Z&se=2026-11-07T18%3A57%3A57Z&sr=c&sp=r&sig=oV4yl9PrK%2FsPQn%2BRKcVEEhYDWlyCsn%2FP2gneqtOigQI%3D) (**Settings**) button.
2. End the end of the **Display** table, enter the following:

| ID | Formula | Heading | Type | CSS | Button |
| --- | --- | --- | --- | --- | --- |
| Delete |  | Delete |  |  | ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Checked_Box_Blue(1).png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A57Z&se=2026-11-07T18%3A57%3A57Z&sr=c&sp=r&sig=oV4yl9PrK%2FsPQn%2BRKcVEEhYDWlyCsn%2FP2gneqtOigQI%3D) (checked) |

> [!NOTE]
> The ID value here is not acting as a Property ID, so it does not need to be in camel case. The field simply needs a value for the button to work.

![Grid view displaying input and output fields for data submission mapping.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/UD_View%20grid%20final.png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A57Z&se=2026-11-07T18%3A57%3A57Z&sr=c&sp=r&sig=oV4yl9PrK%2FsPQn%2BRKcVEEhYDWlyCsn%2FP2gneqtOigQI%3D)
3. Click **Save Component**.

### Configure the Plug-In Component

This [Plug-In](/v1/docs/plug-in-component) component uses the **Deletes Multiple Module Submissions API** to delete the submission and remove it from your dashboard.

1. Drag and drop a **Plug-In** component onto the canvas, placing it below the `submissionId` **Hidden** component.
2. In the **Property ID** and **Canvas** **Label Text** fields, enter `pluginDelete`.
3. From the **Internal Services** drop-down, select **Deletes Multiple Module Submissions**.
4. In the **Data Source URL** field, enter `/fbu/uapi/forms/{{data.moduleId}}/submissions?ids={{data.submissionId}}`.

> Here, you’re adjusting the Data Source URL that populates when you select the Deletes Multiple Module Submissions service. The default value requires that you enter a module ID. The new Data Source URL references the module ID stored in the `moduleID` **Hidden** component. It also references single submission IDs, stored in the `submissionId` **Hidden** component. Now, clicking your **Delete** button deletes one specific submission at a time.

1. From the **Post Trigger** drop-down, enter `pluginGetSubmissions`.

> [!NOTE]
> Doing so triggers `pluginGetSubmissions` **Plug-In** component to refresh your dashboard after every deletion.

![Configuration settings for a plugin, including data source and action triggers.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/UD_plug%20in%20final.png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A57Z&se=2026-11-07T18%3A57%3A57Z&sr=c&sp=r&sig=oV4yl9PrK%2FsPQn%2BRKcVEEhYDWlyCsn%2FP2gneqtOigQI%3D)
2. Click **Save Component**.

### Configure the Decisions Component

Next, you'll add a [Decisions](/v1/docs/decisions-component) component to link your Delete button to the `pluginDelete` Plug-In component.

1. Drag and drop a **Decisions** component onto the canvas, placing it below the `gridView` **ViewGrid** component.
2. In the **Property ID** and **Canvas** **Label Text** fields, enter `ruleButtons`.
3. In the **Inputs** table, enter the following:

| # | Source | Type | Silent |
| --- | --- | --- | --- |
| 1 | buttonClick | exact |  |
| 2 | moduleId | exact | ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Checked_Box_Blue(1).png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A57Z&se=2026-11-07T18%3A57%3A57Z&sr=c&sp=r&sig=oV4yl9PrK%2FsPQn%2BRKcVEEhYDWlyCsn%2FP2gneqtOigQI%3D) (checked) |
| 3 | submissionId | exact | ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Checked_Box_Blue(1).png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A57Z&se=2026-11-07T18%3A57%3A57Z&sr=c&sp=r&sig=oV4yl9PrK%2FsPQn%2BRKcVEEhYDWlyCsn%2FP2gneqtOigQI%3D) (checked) |
4. In the **Outputs** table, enter the following:

| # | Source | Type |
| --- | --- | --- |
| 1 | panel | pageOpen |
| 2 | pluginDelete | trigger |
5. In the **Conditionals** table, enter the following:

| # | buttonClick | moduleId | submissionId | panel_pageOpen | pluginDelete_trigger |
| --- | --- | --- | --- | --- | --- |
| 1 | Delete |  |  |  | GO |
| 2 | View |  |  | =concatenate('/#/display/',moduleId,'/', submissionId , '/',moduleId) |  |

![Configuration settings for decision actions, inputs, outputs, and conditionals in a software interface.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/CD_Decisions(1).png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A57Z&se=2026-11-07T18%3A57%3A57Z&sr=c&sp=r&sig=oV4yl9PrK%2FsPQn%2BRKcVEEhYDWlyCsn%2FP2gneqtOigQI%3D)
6. Click **Save Component**.
7. **Save** your module.

Here's how the completed example looks in the Module Builder:

### ![Dashboard components including buttons and submission options for user interaction.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/UD_final%20module%20final.png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A57Z&se=2026-11-07T18%3A57%3A57Z&sr=c&sp=r&sig=oV4yl9PrK%2FsPQn%2BRKcVEEhYDWlyCsn%2FP2gneqtOigQI%3D)

Here's how the completed example looks in Express View:

![Table displaying user information including names, emails, and dates of birth.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Dashboard%20final%20image.png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A57Z&se=2026-11-07T18%3A57%3A57Z&sr=c&sp=r&sig=oV4yl9PrK%2FsPQn%2BRKcVEEhYDWlyCsn%2FP2gneqtOigQI%3D)

**Classic Designer**

Many dashboards require multiple buttons to perform various actions. For example, one to view a submission and one to delete it.

In this how-to guide, you'll learn how to **display a Delete button in a dashboard**.

> [!TIP]
> This example includes steps for building a simple dashboard. The dashboard retrieves submissions from the following source module: [https://trainingx.unqork.io/#/display/5eb01aa6811bf80215fd706b](https://trainingx.unqork.io/#/display/5eb01aa6811bf80215fd706b).

## Preconfiguration

Begin by setting up basic components for this example.

### Configure the Panel Component

This [Panel](/v1/docs/panel-component) component acts as a container for the components that follow.

1. In the Module Builder, drag and drop a **Panel** component onto the canvas.
2. In the **Property ID** field, enter `panelDashboard`.
3. Click **Save & Close**.

### Configure the Initializer Component

Next, add an [Initializer](/v1/docs/initializer-component) component to trigger a [Plug-In](/v1/docs/plug-in-component) component that you'll set up next.

1. Drag and drop an **Initializer** component inside the `panelDashboard` **Panel** component.
2. In the **Property ID** and **Canvas** **Label Text** fields, enter `initStart`.
3. From the **Trigger Type** drop-down, select **New Submission**.
4. In the **Outputs** table, enter the following:

| # | Property ID | Type | Value |
| --- | --- | --- | --- |
| 1 | pluginGetSubmissions | trigger | GO |

> [!NOTE]
> You’ll configure the `pluginGetSubmissions` **Plug-In** component in the next steps.
5. Click **Save & Close.**

### Configure the First Hidden Component

Now, let's add a [Hidden](/v1/docs/hidden-component) component to store the module ID of your source or submission module.

1. Drag and drop a **Hidden** component inside the `panelDashboard` **Panel** component, below the Initializer component.
2. In the **Property ID** and **Canvas Label Text** fields**,** enter `moduleId`.
3. In the **Default Value** field, enter `5eb01aa6811bf80215fd706b`.

> [!NOTE]
> This module ID is taken from the source module: https://training.unqork.io/#/form/**5eb01aa6811bf80215fd706b**/edit.
4. Click **Save & Close**.

### Configure the Plug-In Component

This [Plug-In](/v1/docs/plug-in-component) component connects the module to the external systems using an API. You’ll use this component to retrieve submissions and display them in your dashboard.

1. Drag and drop a **Plug-In** component inside the `panelDashboard` **Panel** component, below the Hidden component.
2. In the **Property ID** and **Canvas Label Text** fields, enter `pluginGetSubmissions`.
3. From the **Internal Services** drop-down, select **List Submissions for Dashboard.** The **Data Source URL** field gets auto populated.
4. In the **Inputs** table, enter the following:

| Property ID | Mapping |
| --- | --- |
| moduleId | moduleId |
| 'firstName,middleName,lastName,email,dateOfBirth' | fields |

> [!NOTE]
> The first row reference the module ID stored in the `moduleId` **Hidden** component. The second row represents the fields that populate the dashboard. The values entered in the Mapping column (`moduleId` and `fields`) are native values recognized by the Unqork platform.
5. Click **Save.**

### Configure the Second Hidden Component

This [Hidden](/v1/docs/hidden-component) component stores the submission ID.

1. Drag and drop a **Hidden** component inside the `panelDashboard` **Panel** component, below the Plug-In component.
2. In the **Property ID** and **Canvas** **Label Text** fields**,** enter `submissionId`.
3. Set **Store Data in Database** to ![files](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/toggle_ON(15).png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A57Z&se=2026-11-07T18%3A57%3A57Z&sr=c&sp=r&sig=oV4yl9PrK%2FsPQn%2BRKcVEEhYDWlyCsn%2FP2gneqtOigQI%3D) **(****ON)**.
4. Click **Save & Close**.

### Configure the ViewGrid Component

Next, add a [ViewGrid](/v1/docs/viewgrid-component) component to display your dashboard. Notice how the **Action** and **Event** settings create the **View** button.

1. Drag and drop a **ViewGrid** component onto the canvas below the `submissionId` **Hidden** component.
2. In the **Label** field**,** enter `View Grid` and Property Name as `gridView`**.**
3. In the **Action** and **Event** fields, enter `View`.
4. In the **Inputs** table, enter the following:

| ID | Required |
| --- | --- |
| pluginGetSubmissions | ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Checked_Box_Blue(1).png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A57Z&se=2026-11-07T18%3A57%3A57Z&sr=c&sp=r&sig=oV4yl9PrK%2FsPQn%2BRKcVEEhYDWlyCsn%2FP2gneqtOigQI%3D) (checked) |
5. In the **Outputs** table, enter the following:

| ID | Mapping |
| --- | --- |
| submissionId | id |
6. In the **Display** table, enter the following:

| ID | Formula | Heading |
| --- | --- | --- |
| firstName |  | First Name |
| middleName |  | Middle Name |
| lastName |  | Last Name |
| email |  | Email |
| dateOfBirth | =MOMENT(MOMENT(dateOfBirth), 'format','MM/DD/YY') | Date of Birth |

> The Moment.js in the Formula column formats the `dateOfBirth` values as MM/DD/YY.
7. Click **Save**.

## Configuration

Next, you’ll add the second action button by updating the [ViewGrid](/v1/docs/component-library-viewgrid-component) component and configuring a new [Plug-In](/v1/docs/plug-in-component) and [Decisions](/v1/docs/decisions-component) component.

### Update the ViewGrid Component

1. Hover over the `gridView` **ViewGrid** component and click the ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/AppBuildButton_Settings(45).jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A57Z&se=2026-11-07T18%3A57%3A57Z&sr=c&sp=r&sig=oV4yl9PrK%2FsPQn%2BRKcVEEhYDWlyCsn%2FP2gneqtOigQI%3D) (**Settings**) button.
2. At the bottom of the **Display** table, enter the following:

| ID | Formula | Heading | Type | CSS | Button |
| --- | --- | --- | --- | --- | --- |
| Delete |  | Delete |  |  | ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Checked_Box_Blue(1).png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A57Z&se=2026-11-07T18%3A57%3A57Z&sr=c&sp=r&sig=oV4yl9PrK%2FsPQn%2BRKcVEEhYDWlyCsn%2FP2gneqtOigQI%3D) (checked) |

> [!NOTE]
> The ID value here is not acting as a Property ID, so it does not need to be in camel case. The field simply needs a value for the button to work.

![Configuration settings for a ViewGrid, including inputs, outputs, and display options.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/CD_Viewgrid%20final.png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A57Z&se=2026-11-07T18%3A57%3A57Z&sr=c&sp=r&sig=oV4yl9PrK%2FsPQn%2BRKcVEEhYDWlyCsn%2FP2gneqtOigQI%3D)
3. Click **Save**.

### Configure the Plug-In Component

This [Plug-In](/v1/docs/plug-in-component) component uses the **Deletes Multiple Module Submissions API** to delete the submission and remove it from your dashboard.

1. Drag and drop a **Plug-In** component onto the canvas, placing it below the `submissionId` **Hidden** component.
2. In the **Property ID** and **Canvas** **Label Text** fields, enter `pluginDelete`.
3. From the **Internal Services** drop-down, select **Deletes Multiple Module Submissions**.
4. In the **Data Source URL** field, enter `/fbu/uapi/forms/{{data.moduleId}}/submissions?ids={{data.submissionId}}`.

> Here, you’re adjusting the Data Source URL that populates when you select the Deletes Multiple Module Submissions service. The default value requires that you enter a module ID. The new Data Source URL references the module ID stored in the `moduleID` **Hidden** component. It also references single submission IDs, stored in the `submissionId` **Hidden** component. Now, clicking your **Delete** button deletes one specific submission at a time.

1. In the **Post Trigger** drop-down, enter `pluginGetSubmissions`.

> [!NOTE]
> Doing so triggers `pluginGetSubmissions` **Plug-In** component to refresh your dashboard after every deletion.

![Settings panel for a plugin with various configuration options and data inputs.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/CD_pluginDelete.png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A57Z&se=2026-11-07T18%3A57%3A57Z&sr=c&sp=r&sig=oV4yl9PrK%2FsPQn%2BRKcVEEhYDWlyCsn%2FP2gneqtOigQI%3D)
2. Click **Save**.

### Configure the Decisions Component

Next, you'll add a [Decisions](/v1/docs/decisions-component) component to link your Delete button to the pluginDelete Plug-In component.

1. Drag and drop a **Decisions** component onto the canvas, placing it below the `gridView` **ViewGrid** component.
2. In the **Property ID** and **Canvas** **Label Text** fields, enter `ruleButtons`.
3. In the **Inputs** table, add the following:

| Source | Type | Silent |
| --- | --- | --- |
| buttonClick | exact |  |
| moduleId | exact | ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Checked_Box(7).png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A57Z&se=2026-11-07T18%3A57%3A57Z&sr=c&sp=r&sig=oV4yl9PrK%2FsPQn%2BRKcVEEhYDWlyCsn%2FP2gneqtOigQI%3D) (checked) |
| submissionId | exact | ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Checked_Box(7).png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A57Z&se=2026-11-07T18%3A57%3A57Z&sr=c&sp=r&sig=oV4yl9PrK%2FsPQn%2BRKcVEEhYDWlyCsn%2FP2gneqtOigQI%3D) (checked) |
4. In the **Outputs** table, add the following:

| Source | Type |
| --- | --- |
| panel | pageOpen |
| pluginDelete | trigger |
5. In the **Micro Decisions** table, add the following:

| buttonClick | moduleId | submissionId | panel_pageOpen | pluginDelete_trigger |
| --- | --- | --- | --- | --- |
| Delete |  |  |  | GO |
| View |  |  | =concatenate('/#/display/',moduleId,'/', submissionId , '/',moduleId) |  |

![Settings panel displaying property IDs, actions, and input/output values for decisions.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/CD_Decisions%20final.png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A57Z&se=2026-11-07T18%3A57%3A57Z&sr=c&sp=r&sig=oV4yl9PrK%2FsPQn%2BRKcVEEhYDWlyCsn%2FP2gneqtOigQI%3D)
6. Click **Save**.
7. **Save** your module.

Here'show the completed example looks in the Module Builder:

### ![Dashboard interface displaying module components and options for managing submissions and rules.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/CD_final%20module%20fnal.png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A57Z&se=2026-11-07T18%3A57%3A57Z&sr=c&sp=r&sig=oV4yl9PrK%2FsPQn%2BRKcVEEhYDWlyCsn%2FP2gneqtOigQI%3D)

Here's how the completed example looks in Express View:

![Table displaying user information including names, emails, and dates of birth.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Dashboard%20final%20image.png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A57Z&se=2026-11-07T18%3A57%3A57Z&sr=c&sp=r&sig=oV4yl9PrK%2FsPQn%2BRKcVEEhYDWlyCsn%2FP2gneqtOigQI%3D)

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.

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.

A Property ID is the unique field ID used by Unqork to track and link components in your module.

Deteremines how the component triggers.

The component fires when the page or called module loads without an existing submission ID. Dashboards and remote execute modules are great uses for this trigger.

APIs (application programming interfaces) are a set of protocols and definitions developers use to build and integrate application software. APIs act as the connective tissue between products and services.

Enter inputs components and actions you want the component to perform..

A JavaScript date library that lets you parse, validate, manipulate, and reformat dates.

A naming convention for computer programming. Use camelCase for Property IDs, for example: newUser, lastName, & rdoButton.

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.

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 .

A Property ID is the unique field ID used by Unqork to track and link components in your module.