DemandFlow Support Centre

PJGATE: Project Gate

ReferenceEntity Reference16/04/2026Updated 16/04/2026
The PJGATE entity represents a gate evaluation instance recording the results of a governance checkpoint applied to a specific project.

PJGATE: Project Gate

The PJGATE entity represents a gate evaluation instance recording the results of a governance checkpoint applied to a specific project.

Default definition. This article describes the default PJGATE 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 PJGATE.

Entity properties

PropertyValue
Entity codePJGATE
Display nameProject Gate
PluralProject Gates
Level488

Use cases

PJGATE records are children of PJ (comboKey format SUB|PJ). Each record represents one gate template being evaluated against a project. The results JSON property contains the item-by-item evaluation snapshot. The attempts JSON array stores previous evaluation runs for audit trail and re-evaluation history. Created and updated by the runGateReview toolbar function on PJ. Status transitions: Pending (initial), Failed (checks not met), Passed (all mandatory checks pass), Overridden (mandatory failures overridden by authorised user with justification).

Fields

Gate Result

FieldTypeRequiredNotes
nametextGate Name. Read-only.
templateNametextTemplate. Read-only.
templateIdtextTemplate ID. Read-only.
statusenumStatus. Valid ids: Pending (Pending), Passed (Passed), Failed (Failed), Overridden (Overridden).
scorenumberScore (%). Read-only.
requestedByreference → userRequested By. Read-only.
requestedDatedateRequested Date. Read-only.
approvedByreference → userApproved By. Read-only.
approvedDatedateApproved Date. Read-only.
overrideJustificationtext (multi-line)Override Justification. Read-only.

Relationships

  • Embedded arrays: array, array. Each entry is a sub-record stored inline on this object.

Creating a Project Gate via the API

POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json

{
  "entity":   "PJGATE",
  "level":    488,
  "comboKey": "SUB:<your-sub-id>|ENT:",
  "name": "Example"
}

Listing PJGATE records

# All project gates in your tenant
GET /v1/entities/PJGATE/SUB

See also

pjgateproject gateproject gatesprojectgate

Was this article helpful?

← Back to Knowledge Base