# US 2025/0165706 A1 · Database model which provides management of custom fields and methods and apparatus therfor

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2025/0165706 A1
- Document ID: US20250165706A1
- Status: Published application
- Kind: A1
- Application number: 19/028,791
- Filed: 2025-01-17
- Published: 2025-05-22
- Earliest claimed: 2017-07-11
- Assignees: Asana, Inc.
- Applicants: Asana, Inc.
- Inventors: Eric Seth Pelz; Gregory Heath Slovacek; Rosario John Aquino; Jacqueline Frances Bavaro; Nicholas William Fassler
- Web page: https://patentgrep.com/patent/US20250165706A1

## CPC

- G06F 40/177: of tables; using ruled lines
- G06F 3/0482: Interaction with lists of selectable items, e.g. menus
- G06F 16/211: {Schema design and management}
- G06F 16/212: {with details for data modelling support}
- G06F 16/2456: {Join operations}
- G06F 16/252: {between a Database Management System and a front-end application}
- G06Q 10/063118: {Staff planning in a project environment}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

A data model for managing custom fields for tasks in projects. The custom fields can be defined and shared across an organization, and are always unique. Each type of custom field is an object that is subclass of a generic object. Other objects define attributes of the custom fields and assign values to the attributes. The data model allows the custom fields to be preserved and managed across multiple projects and users.

## Claims

### Claim 1

A system configured to manage a custom field of a work object, the system comprising:
non-transitory electronic storage storing:
a work object for work managed by a computing environment, the work object including a unique work ID;
a first object specifying a definition of a custom field, the first object including a unique first object ID; and
a second object including i) a value of the custom field for the work in accordance with the definition of the custom field as applied to the work object through a join of the first object and the work object, ii) the unique work ID so that the value of the custom field specified in the second object is associated with the work object, and iii) the unique first object ID so that the value of the custom field specified in the second object is associated with the definition of the custom field specified by the first object; and
one or more physical processors configured by computer-readable instructions to:
effectuate presentation of the value for the custom field for the work in a user interface of the computing environment by accessing the second object and retrieving the value from the second object, wherein the second object is accessed to present the value for the custom field for the work based on the unique work ID included in the second object being associated with the work object, and the unique first object ID included in the second object being associated with the custom field.

### Claim 2 (depends on 1)

The system of claim 1, wherein the one or more physical processors are further configured by the computer-readable instructions to:
define a second work object representing a second work; and
define a work setting object specifying specific settings, the work setting object representing a join between the second work object and the first object.

### Claim 3 (depends on 2)

The system of claim 2, wherein the first object specifies the custom field has selectable value options.

### Claim 4 (depends on 1)

The system of claim 1, wherein the second object is expressed in a form of a JavaScript Object Notation (JSON) blob.

### Claim 5 (depends on 1)

The system of claim 1, wherein the second object is expressed in a form of a join object.

### Claim 6 (depends on 1)

The system of claim 1, wherein the definition of the custom field further indicates one or more of a tracking number, a category, an owner, or dependencies.

### Claim 7 (depends on 1)

The system of claim 1, wherein the work object has a property that contains values of a set of custom fields associated with the work.

### Claim 8 (depends on 1)

The system of claim 1, wherein responsive to an event that the work no longer inherits the value of the custom field because of editing, the value of the custom field is maintained in association with the work.

### Claim 9 (depends on 1)

The system of claim 1, wherein the one or more physical processors are further configured by the computer-readable instructions to receive edits to remove a specific selectable value option from a custom field option proto, and set an archive attribute to preserve the specific selectable value option.

### Claim 10 (depends on 9)

The system of claim 9, wherein the specific selectable value option is displayed in the user interface to indicate that is has been removed.

### Claim 11

A method to manage a custom field of a work object, the method comprising:
storing a work object for work managed by a computing environment, the work object including a unique work ID;
storing a first object specifying a definition of a custom field, the first object including a unique first object ID;
storing a second object including i) a value of the custom field for the work in accordance with the definition of the custom field as applied to the work object through a join of the first object and the work object, ii) the unique work ID so that the value of the custom field specified in the second object is associated with the work object, and iii) the unique first object ID so that the value of the custom field specified in the second object is associated with the definition of the custom field specified by the first object; and
effectuating presentation of the value for the custom field for the work in a user interface of the computing environment by accessing the second object and retrieving the value from the second object, wherein the second object is accessed to present the value for the custom field for the work based on the unique work ID included in the second object being associated with the work object, and the unique first object ID included in the second object being associated with the custom field.

### Claim 12 (depends on 11)

The method of claim 11, further comprising:
defining a second work object representing a second work; and
defining a work setting object specifying specific settings, the work setting object representing a join between the second work object and the first object.

### Claim 13 (depends on 12)

The method of claim 12, wherein the first object specifies the custom field has selectable value options.

### Claim 14 (depends on 11)

The method of claim 11, wherein the second object is expressed in a form of a JavaScript Object Notation (JSON) blob.

### Claim 15 (depends on 11)

The method of claim 11, wherein the second object is expressed in a form of a join object.

### Claim 16 (depends on 11)

The method of claim 11, wherein the definition of the custom field further indicates one or more of a tracking number, a category, an owner, or dependencies.

### Claim 17 (depends on 11)

The method of claim 11, wherein the work object has a property that contains values of a set of custom fields associated with the work.

### Claim 18 (depends on 11)

The method of claim 11, further comprising: responsive to an event that the work no longer inherits the value of the custom field because of editing, maintaining the value of the custom field in association with the work.

### Claim 19 (depends on 11)

The method of claim 11, further comprising receiving edits to remove a specific selectable value option from a custom field option proto, and setting an archive attribute to preserve the specific selectable value option.

### Claim 20 (depends on 19)

The method of claim 19, wherein the specific selectable value option is displayed in the user interface to indicate that is has been removed.
