PATENTA: Jurisdiction Application
The PATENTA entity represents a jurisdiction-specific patent application tracking filing, prosecution, grant dates, status, and assigned attorney.
Default definition. This article describes the default
PATENTA 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 PATENTA.Entity properties
| Property | Value |
|---|---|
| Entity code | PATENTA |
| Display name | Jurisdiction Application |
| Plural | Jurisdiction Applications |
| Level | 430 |
Use cases
Child entity of PATENT for tracking applications across different jurisdictions. Three-column layout: left has application details (creator, name, jurisdiction objectLookup to PATENTJ, application/publication/grant numbers, active flag), middle has prosecution dates (filing through grant/expiry plus office action and attorney workflow dates), right has status (lifecycle status, RAG with colours) and ownership (assignee, attorney, family ID). Supports Notes and Documents panels for jurisdiction-specific correspondence. Linked to PATENT via SUB|PAT comboKey.
Fields
General
| Field | Type | Required | Notes |
|---|---|---|---|
ownerId | reference → user | Created by. Read-only. | |
name | text | Application name. | |
jurisdiction | reference → PATENTJ | Yes | Jurisdiction. |
applicationNumber | text | Application number. | |
publicationNumber | text | Publication number. | |
grantNumber | text | Grant number. | |
active | enum | Active. Valid ids: 1 (Yes), 0 (No). | |
filingDate | date | Application filed. | |
dateSearchReport | date | Search report received. | |
dateExamRequested | date | Examination requested. | |
dateOfficeAction | date | Office action received. | |
dateOfficeActionDue | date | Office action response due. | |
dateOfficeActionFiled | date | Office action response filed. | |
dateAttorney | date | Submitted to attorney. | |
dateAttorneyAck | date | Attorney acknowledgement. | |
dateAttorneyReview | date | Review attorney progress. | |
publicationDate | date | Publication date. | |
grantDate | date | Notification of grant. | |
grantDateCertificate | date | Certificate of grant. | |
expiryDate | date | Expiry date. | |
status | enum | Yes | Status. Valid ids: filed (Filed), published (Published), examination (Under Examination), granted (Granted), refused (Refused), withdrawn (Withdrawn), lapsed (Lapsed). |
rag | enum | Yes | RAG. Valid ids: Green - on track (Green - on track), Amber - at risk (Amber - at risk), Red - significant challenges (Red - significant challenges). |
assigned_to | reference → user | Assigned to. | |
attorney | text | Local attorney / agent. | |
familyId | text | Family ID. | |
totalCost | number | Total cost. |
Additional panels
- Activity timeline panel attached.
- Documents. Field
attachments.
Relationships
- Lookups:
jurisdictionpoints atPATENTJrecord.
Creating a Jurisdiction Application via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "PATENTA",
"level": 430,
"comboKey": "SUB:<your-sub-id>|ENT:",
"jurisdiction": "",
"status": "filed",
"rag": "Green - on track",
"name": "Example"
} Listing PATENTA records
# All jurisdiction applications in your tenant
GET /v1/entities/PATENTA/SUB