SCOREMODEL: Scoring Model
The SCOREMODEL entity: A configurable multi-criteria scoring framework used to rank and prioritise projects at the portfolio level.
Default definition. This article describes the default
SCOREMODEL 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 SCOREMODEL.Entity properties
| Property | Value |
|---|---|
| Entity code | SCOREMODEL |
| Display name | Scoring Model |
| Plural | Scoring Models |
| Level | 485 |
Use cases
SCOREMODEL defines the weighted criteria used to evaluate projects against strategic, financial, risk, feasibility, resource, customer and regulatory dimensions. Each model is re-usable across portfolios. scores are captured on PROJSCORE records that reference the model.
Criteria carry a weight (1-100) and a scoreType describing the scale the evaluator uses. Models can be Draft while being designed, Active when in use, and Archived when retired.
Fields
Model
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Name |
description | text (multi-line) | Description | |
status | enum | Status Valid ids: active (Active), draft (Draft), archived (Archived). | |
gatePassThreshold | number | Optional. Minimum total score required for a project to pass a gate review cleanly. Projects below this are flagged in the gate popout. Leave blank to disable. |
Relationships
- No declared relationships in the default definition.
Creating a Scoring Model via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "SCOREMODEL",
"level": 485,
"comboKey": "SUB:|ENT:",
"name": "Example name",
"description": "Example Description",
"status": "active",
"gatePassThreshold": 1
} Listing Scoring Models records
GET /v1/entities/SCOREMODEL/SUB