---
title: "How to: Apply Data Models to a Case Management Application"
slug: "how-to-apply-data-models-to-a-case-management-application"
updated: 2025-09-25T20:38:47Z
published: 2025-09-25T20:38:47Z
canonical: "docs.unqork.io/how-to-apply-data-models-to-a-case-management-application"
---

> ## 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: Apply Data Models to a Case Management Application

## Overview

In this how-to guide, you'll learn how to bind a set of Data Models with schemas, provided by the ACME company, to a [module](/v1/docs/introduction-to-the-module-builder). Once bound, Creators can configure [components](/v1/docs/module-builder-component-library) defined by the schemas in the Module Builder.

> [!TIP]
> To learn more about creating Data Models, view our [How to: Create Data Models for a Case Management Application](/v1/docs/how-to-create-data-models-for-a-case-management-application) article.

## What You'll Learn

In this article, you’ll learn how to bind Data Models to a module. You'll also learn to add and configure predefined schema field components in the Module Builder.

## What You Need

In this how-to guide, you need the following:

- 1 [Workspace](/v1/docs/introduction-to-workspaces)
- 2 [Data Models](/v1/docs/introduction-to-unqork-data-modeling)
- 1 [Module](/v1/docs/introduction-to-the-module-builder)

## Associate the Data Models to a Module

To use a Data Model, you must assign it to a module in the **Module** **Settings**. This creates a new tab in the Module Builder called Data.

To assign a Data Model to a module:

1. In Workspaces view, navigate to and select the **Workspace** that contains the Data Model you want to apply.
2. From the **Applications** tab of your workspace, select or create the [module-type](//docs/working-with-module-type-apps) application where you want to apply your Data Model.
3. From the Modules tab of your application, click the ··· (**ellipsis**) button.
4. Select (**Settings**). The Settings modal displays.
5. From the **Data Model****s** drop-down, select **application-model** and **product-model**.
6. Click **Save**. The module refreshes and the Data tab displays above the component tray.

[Video](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/DM_InsuranceApp_AssociateModel.webm?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)

## Adding Data Model Elements to a Module

Once a module has a Data Model, Creators can use the Data tab to drag and drop schema field components predefined by the Data Model’s schema. The schema’s predefined values ensure the data fields collect data the same way every time.

### What You Need

- 5 **application-model** schema field components
- 3 **product-model** schema field components
- 1 [Button](/v1/docs/button-component) component

### Add the Schema Field Components

Unlike regular components, schema field components are predefined by each Data Model's schema. You can customize how these fields are displayed on the canvas, but the **D****ata** and **Validation** settings are locked in each components' configuration window.

To add schema field components to a module:

1. From the Module Builder, click the Data tab.
2. From the **application-model** panel, drag and drop the **Application Id** schema field component onto the canvas.

[Video](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/DM_InsuranceApp_Add_AppID.webm?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. Repeat this process with the following schema field components: **Application Name**, **Investor Type**, **Account Type**, and **Cases**.
4. Expand the **product-model** panel.
5. Drag and drop the following schema field components onto the canvas: **Product Id**, **Product Name**, and **Product Type**.

[An animted image displaying the Module Builder, the Product-Model drop-down is selected and the three schema field components are dragged onto the canvas.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/DM_InsuranceApp_Add_ProdID.webm?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. **Save** your module.

### Configure the Button Component

Now that the module has all the data fields our fictional ACME company needs to collect, you'll configure a Button component. In Express View, end-users use the button to save their applications.

To add a Button component to a module:

1. Drag and drop a **Button** component onto the canvas, placing it below the **product-model** schema field components.
2. In the Property ID field, enter **btnSubmit**.
3. Set Restrict Single Click to (ON).

![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/DM_InsuranceApp_ButtonRestrict_thumb_0_0.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)
4. To the left of the component's configuration window, click **Actions**.
5. In the **Success Message** field, enter `Your Application Has Been Submitted`.
6. Click **Save & Close**.
7. **Save** your module.

You now have a module containing schema fields from Data Models. When this module captures data, individual records save against the Data Model. You can find these records in the [Record Collections Viewer](/v1/docs/record-collections-viewer).

## Resources

- [Introduction to Data Modeling](/v1/docs/introduction-to-unqork-data-modeling)
- [Schemas Viewer](/v1/docs/schemas-viewer)
- [Data Models Viewer](/v1/docs/data-models-viewer)
- [Apply Data Modeling to a Module](/v1/docs/apply-data-modeling-to-a-module)
- [JSON Schema Component Mapping](/v1/docs/json-schema-component-mapping)
- [How to: Create Data Models for a Case Management Application](/v1/docs/how-to-create-data-models-for-a-case-management-application)
- [How to: Query Data Model Records Data](/v1/docs/how-to-query-data-model-records-data)
- [Record Collections Viewer](/v1/docs/record-collections-viewer)

Also known as Unqork Users, or Designer Users; is anyone who is inside the Unqork platform.

A modal is a window that appears on top of the content you are currently viewing.

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.

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.

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