---
sourceDocument: Brazil Retail Industry
sourceDocumentLink: https://www.servicenow.com/docs/r/retail-industry

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Retail Industry

ft:clusterId :

    - rahi

bundleId :

    - rahi

workflow :

    - Customer and Industry


---

# Project task data model

# Project task data model {#ariaid-title1}

Release version: Brazil  
Updated September 17, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
The project and project task records that Retail reads, the fields it displays, and the three fields it
writes.

## Table ownership {#rahi-retail-spm-project-tasks-data-model__spm-project-tasks-data-model-tables}

Project tasks are stored on tables that the Customer Service Management (CSM) and Retail Strategic Portfolio Management Suite applications own. Retail defines no columns on either table.
{#rahi-retail-spm-project-tasks-data-model__table_spm_project_tasks_tables__entry__3}

| Table | Access | Purpose |
|-|-|-|
| `customer_project` | Read | The store life cycle project. Shown in the project list and on the project page. |
| `customer_project_task` | Read and write | The work items within a project. Shown in the task lists and on the task page. |
[Table 1. Tables used for project tasks]

{#rahi-retail-spm-project-tasks-data-model__table_spm_project_tasks_tables}

Retail writes only three fields, and only through the task
actions: `state`, `assigned_to`, and
`assignment_group`. Every other field is read-only from a store
persona's perspective. The artifacts that surface these tables install only when the
App SPM Retail plugin is present.

## Fields used by this feature {#rahi-retail-spm-project-tasks-data-model__spm-project-tasks-data-model-fields}

{#rahi-retail-spm-project-tasks-data-model__table_spm_project_tasks_fields__entry__3}

| Field | Table | Used for |
|-|-|-|
| `service_organization` | `customer_project` | Identifies the store that the project belongs to. Used to build the portal breadcrumb. |
| `project_manager`, `state`, `description`, `end_date` | `customer_project` | Project card and project page fields. |
| `visible_to_customer` | `customer_project_task` | The visibility gate. Portal lists filter on this field, so an unflagged task never reaches a store persona. |
| `customer_project` | `customer_project_task` | Links a task to its project. Rendered as a link in the task header. |
| `parent` | `customer_project_task` | Child tasks. Also walked to build the breadcrumb chain of ancestor tasks. |
| `rollup`, `top_task` | `customer_project_task` | Determine whether a task can be closed. |
| `state` | `customer_project_task` | Gates the task actions, and is set when a persona closes a task. |
| `assigned_to`, `assignment_group` | `customer_project_task` | Set by the assignment actions. |
| `number`, `short_description`, `priority`, `end_date` | `customer_project_task` | Task list columns and task card fields. |
[Table 2. Project and project task fields]

{#rahi-retail-spm-project-tasks-data-model__table_spm_project_tasks_fields}  
Tip:  
The task field labeled Due date on the mobile task card reads the `end_date` field, not `planned_end_date`. The `planned_end_date` field is inherited but isn't populated on project task records.

## Task states that close a task {#rahi-retail-spm-project-tasks-data-model__spm-project-tasks-data-model-states}

A project task is treated as closed, and its actions are withdrawn, in three
states:

* Closed Complete
* Closed Incomplete
* Closed Skipped

{#rahi-retail-spm-project-tasks-data-model__ul_spm_terminal_states}

In any other state, including Pending, the task is open and its actions remain
available subject to the persona's access.

## Relationships {#rahi-retail-spm-project-tasks-data-model__spm-project-tasks-data-model-relationships}

* A project task references its project through the `customer_project` field.
* A project task can have child project tasks on the same table, through the `parent` field. The task page lists the immediate children.
* A project is associated with a store through its `service_organization` field, which resolves to a retail organization.
{#rahi-retail-spm-project-tasks-data-model__ul_spm_relationships}
**Related concepts**   

* [Project tasks in Retail](https://www.servicenow.com/docs/5Bv_n72Z6nphxp28_poJGg "Store associates and managers can view and act on the project work behind a store opening, closing, renovation, or relocation without leaving the Retail.")  
**Related reference**   

* [Roles and visibility for project tasks](https://www.servicenow.com/docs/VRYeJfqknVo_uH3ei8pYog "Roles determine which store personas see project tasks in Retail, which surfaces they reach, and which actions they can take on a task.")