PJGATETPL: Gate Template
The PJGATETPL entity represents a reusable gate template defining the checklist criteria that must be satisfied before a project can proceed past a governance checkpoint.
PJGATETPL 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 PJGATETPL.Entity properties
| Property | Value |
|---|---|
| Entity code | PJGATETPL |
| Display name | Gate Template |
| Plural | Gate Templates |
| Level | 486 |
Use cases
PJGATETPL defines gate types (e.g. IT Project Initiation, Marketing Campaign Launch). The matchCriteria JSON property contains rules for auto-suggesting this template to projects based on their properties (pmTypes, portfolio, etc). Each template has child PJGATEITEM records defining the individual checklist items. When a gate review is run on a project (runGateReview toolbar function), matching templates are suggested and checklist items are evaluated against project data. The stage field indicates which project lifecycle phase this gate applies to. approverRoles and mandatoryOverrideRoles control who can approve gates and override mandatory failures.
Fields
General
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Template Name. |
description | text (multi-line) | Describe the purpose and scope of this gate template. | |
stage | enum | Lifecycle Stage. Valid ids: initiation (Initiation), planning (Planning), execution (Execution), closure (Closure). | |
category | text | Category. | |
status | enum | Status. Valid ids: active (Active), draft (Draft), archived (Archived). | |
approverRoles | array of references → user | Users who can approve this gate on a project. | |
mandatoryOverrideRoles | array of references → user | Users who can override mandatory gate failures. |
Additional panels
- matchcriteria panel.
Relationships
- Related lists:
PJGATEITEMvia formatSUB|PJGATETPL.
Creating a Gate Template via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "PJGATETPL",
"level": 486,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example",
"description": "Long description text.",
"stage": "initiation",
"category": "Example text"
}Listing PJGATETPL records
# All gate templates in your tenant
GET /v1/entities/PJGATETPL/SUB