PATENTJ: Jurisdiction
The PATENTJ entity represents a patent jurisdiction (e.g., USPTO, EPO) used as a reference lookup for patent applications.
Default definition. This article describes the default
PATENTJ definition shipped with DemandFlow. Administrators can add, remove, rename, or re-type fields, change which ones are required, and alter the layout from the Definitions screen in Settings. Your tenant's current schema may differ from what is shown here. To read the current definition at any time, GET the DEFINITION object whose id matches PATENTJ.Entity properties
| Property | Value |
|---|---|
| Entity code | PATENTJ |
| Display name | Jurisdiction |
| Plural | Jurisdictions |
| Level | 430 |
Use cases
Simple reference entity for patent jurisdictions. Single-column layout with creator (singleuser, readonly) and name fields. Referenced by PATENTA via objectLookup with comboKey: 2, enabling jurisdiction-specific application tracking. Supports permissions and bulk actions. Provides a controlled list of patent offices/jurisdictions.
Fields
General
| Field | Type | Required | Notes |
|---|---|---|---|
ownerId | reference → user | Created by. Read-only. | |
name | text | Yes | Jurisdiction name. |
code | text | Country / office code. | |
office | text | Patent office. | |
region | enum | Region. Valid ids: europe (Europe), americas (Americas), asia-pacific (Asia-Pacific), other (Other). | |
website | text | Patent office website. | |
renewalInfo | text (multi-line) | Renewal rules & deadlines. |
Relationships
- No declared relationships in the default definition.
Creating a Jurisdiction via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "PATENTJ",
"level": 430,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example",
"code": "EX-001",
"office": "Example text",
"region": "europe"
}Listing PATENTJ records
# All jurisdictions in your tenant
GET /v1/entities/PATENTJ/SUB