DemandFlow Support Centre

SCENARIO: Scenario

ReferenceEntity Reference16/04/2026Updated 16/04/2026
A named what-if variant of a portfolio's project mix, capturing which projects are included and their adjusted budgets / timelines / priorities for comparison against baseline.

SCENARIO: Scenario

The SCENARIO entity: A named what-if variant of a portfolio's project mix, capturing which projects are included and their adjusted budgets / timelines / priorities for comparison against baseline.

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

Entity properties

PropertyValue
Entity codeSCENARIO
Display nameScenario
PluralScenarios
Level495

Use cases

SCENARIO is a child of PORT (comboKey SUB|PORT). Each SCENARIO holds a snapshot-style set of SCENARIOLINE records. one per project.

which the planner toggles in/out and tweaks. Scenarios are non-destructive: they never change the underlying PJ records, only surface comparative totals.

Fields

Basic Information

FieldTypeRequiredNotes
reftextRead-only. Ref
nametextYesScenario Name
descriptiontext (multi-line)Description
statusenumYesStatus Valid ids: draft (Draft), active (Active), approved (Approved), archived (Archived).

Snapshot

FieldTypeRequiredNotes
baselineDatedatePoint-in-time the scenario was branched from
ownerIdreference → userRead-only. Created By

Additional panels

  • 1 dashboard panel rendered from custom functions.

Relationships

  • Lookups: ownerId points at a user.
  • Related lists: SCENARIOLINE (format SUB|PORT|SCENARIO).
  • Parent: typically a child of PORT via comboKey.

Creating a Scenario via the API

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

{
  "entity":   "SCENARIO",
  "level":    495,
  "comboKey": "SUB:|PORT:|ENT:",
  "name":    "Example name",
  "status":    "draft",
  "description":    "Example Description",
  "baselineDate":    "2026-01-01"
}

Listing Scenarios records

GET /v1/entities/SCENARIO/SUB
GET /v1/entities/SCENARIO/SUB:<your-sub-id>|PORT:<parent-id>

See also

scenarioscenariosentitydefinitionreference

Was this article helpful?

← Back to Knowledge Base