--- title: "How to: Create Data Models for a Case Management Application" slug: "how-to-create-data-models-for-a-case-management-application" updated: 2025-09-25T20:39:54Z published: 2025-09-25T20:39:54Z canonical: "docs.unqork.io/how-to-create-data-models-for-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: Create Data Models for a Case Management Application ## Overview In this how-to guide, you'll explore a simple Data Model for a case management application. A fictional company called ACME wants you to use two predefined schemas to create two data models. Creators can then use the data models in a [module](/v1/docs/introduction-to-the-module-builder) to capture new [applications](/v1/docs/introduction-to-unqork-applications). ## What You’ll Learn In this article, you’ll learn how to create a set of data models for a case management application using predefined schemas. ## What You Need For this how-to guide, you need the following: - 1 [Workspace](/v1/docs/introduction-to-workspaces) - 2 JSON Schemas ## Import and Bind Schemas to Data Models Unqork Data Models use a JSON Schema to define the requirements for storing and validating data in applications. For this how-to guide, you’ll download and import two predefined JSON Schemas. Later, you’ll bind the schemas to Unqork Data Models. Then, you can use them in your modules to insert predetermined fields set by the schemas. ### Download the Company's Schema Files The insurance company has created two schemas for you to use when building your Data Model. The **application-schema.json** schema file contains fields that Creators can use to capture case-specific data. The **product-schema.json** schema file contains fields used to capture product information, like loan type. Right-click and save the following files to an accessible location on your computer: #### Application-schema.json ```json {  "title": "Application",  "type": "object",  "properties": {    "ApplicationId": {      "type": "string"    },    "ApplicationName": {      "type": "string"    },    "InvestorType": {      "type": "string"    },    "AccountType": {      "type": "string",      "enum": [        "Pension",        "401K",        "IRA"      ]    },    "Cases": {      "type": "array",      "items": {        "type": "object",        "properties": {          "caseId": {            "type": "string",            "minLength": 5          },          "caseName": {            "type": "string",            "maxLength": 10          },          "caseStatus": {            "type": "integer"          }        }      }    }  } } ``` #### Product-schema.json ```json {  "title": "Product",  "type": "object",  "properties": {    "ProductId": {      "type": "string"    },    "ProductName": {      "type": "string"    },    "ProductType": {      "type": "string",      "enum": [        "Mortgage",        "Loan",        "Other"      ]    }  } } ``` ### Import the Schema Files Into Unqork Import the **application-schema** and **product-schema** schemas using the **Schemas** page. After importing the schemas, publish and bind them to Data Models using the **Data Model****s** page. > [!TIP] > To learn more about using the Schema page, view our [Upload, Modify, and Publish JSON Schemas](/v1/docs/schemas-viewer) article. First, import the **application-schema.json** schema. Then repeat the process for the **product-schema.json** schema: 1. In **Workspaces** view, navigate to and select your Workspace. 2. To the left of the page, select **Schemas**. 3. At the top right, click **+ Import Schema**. ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/DM_InsuranceApp_ImportSchema_thumb_0_0.jpg?sv=2026-02-06&spr=https&st=2026-11-06T21%3A38%3A18Z&se=2026-11-06T22%3A38%3A18Z&sr=c&sp=r&sig=C88MQaQmzlbgTPN1TwAw%2B7jWz6X1b9oOAg%2Fg7sMZja0%3D) 4. In the **Schema Name** field, enter `application-schema`. 5. Under **Upload Schema**, drag and drop or browse and select the **application-schema.json** file from your computer. ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/DM_InsuranceApp_ImportSchema2_thumb_0_0.jpg?sv=2026-02-06&spr=https&st=2026-11-06T21%3A38%3A18Z&se=2026-11-06T22%3A38%3A18Z&sr=c&sp=r&sig=C88MQaQmzlbgTPN1TwAw%2B7jWz6X1b9oOAg%2Fg7sMZja0%3D) 6. Click **Import**. The **application-schema** schema displays on the **Schemas** page. > [!NOTE] > A warning message displays in the upload modal if the uploaded schema contains invalid JSON. 7. Repeat this process for the product-schema.json file. In the **Schema Name** field, enter product-schema. ### Publish the Schemas Each schema begins in a draft state. In this draft state, you can adjust the schema values as needed. When creating your schemas, it's important to verify all aspects of it before publishing. For this example, the schema does not need to be adjusted and is ready to be published. First, publish the **application-schema** schema, then repeat the process for the **product-schema** schema: 1. From the Schemas page, select **application-schema** from the schemas list. The Schema Information panel displays. 2. Click **Publish**. > [!WARNING] > After publishing a schema, you cannot edit it. Confirm your schema is ready before publishing. [An animated image showing the Schemas page, a schema is selected and the Publish button is pressed.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/DM_InsuranceApp_PublishSchema.webm?sv=2026-02-06&spr=https&st=2026-11-06T21%3A38%3A18Z&se=2026-11-06T22%3A38%3A18Z&sr=c&sp=r&sig=C88MQaQmzlbgTPN1TwAw%2B7jWz6X1b9oOAg%2Fg7sMZja0%3D) 3. Click **Yes, Publish**. The **application-schema** schema’s state changes from **Draft** to **Published**. 4. Repeat this process for the **product-schema** schema. ### Create the Data Models and Bind the Schemas Now that you have published two unique schemas, you'll create two Data Models and bind them to the schemas. First, create and bind the **application-model** Data Model, then repeat the process for the **product-model** Data Model: 1. To the left of your Workspaces view, click Data Models. 2. At the top right, click **+ Create** **Data Model**. 3. In the **Data Model** **Name** field, enter `application-model`. You’ll reference this name when you assign a Data Model to a module. 4. From the **Select Schema** drop-down, select **application-schema**. [An animated image showing the Create Data Model modal, the Select Schema drop-down is highlighted, then the application-schema schema is selected.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/DM_InsuranceApp_CreateDM.webm?sv=2026-02-06&spr=https&st=2026-11-06T21%3A38%3A18Z&se=2026-11-06T22%3A38%3A18Z&sr=c&sp=r&sig=C88MQaQmzlbgTPN1TwAw%2B7jWz6X1b9oOAg%2Fg7sMZja0%3D) 5. Click **Create**. 6. Repeat this process for the **product-schema** schema. In the **Data Model** **Name** field, enter `product-model`. From the **Select Schema** drop-down, select **product-schema**. You now have two Data Models bound to schemas. To learn how to bind your Data Models to a module, view our [How to: Apply Data Models to a Case Management Application](/v1/docs/how-to-apply-data-models-to-a-case-management-application) article. ## 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: Apply Data Models to a Case Management Application](/v1/docs/how-to-apply-data-models-to-a-case-management-application) - [How to: Query Data Model Records Data](/v1/docs/how-to-query-data-model-records-data) Also known as Unqork Users, or Designer Users; is anyone who is inside the Unqork platform. JSON (JavaScript Object Notation) is an open standard file and data interchange format. Unqork uses JSON for submission (record) data. A modal is a window that appears on top of the content you are currently viewing.