DemandFlow Support Centre

ACTION: Action

An action item assigned to a person with due date, priority, and links to originating meetings and decisions.

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

Entity properties

Property	Value
Entity code	`ACTION`
Display name	Action
Plural	Actions
Level	540

Use cases

ACTION tracks work items arising from governance activities. The combo2 definitions provide secondary indexes by assigned_to (USER) and status (STATUS), enabling filtered views like 'my actions' and 'overdue actions'. Actions link to their originating meeting (MEETING lookup) and related decision (DECISION lookup) for traceability. The comboKey relationship (SUB|PJ or SUB|PJ|MEETING) scopes actions to a project and optionally a meeting. The status workflow (Open > In Progress > Completed > Deferred > Cancelled) with priority levels (Low, Normal, High, Critical) supports triage.

Fields

General: Action Details

Field	Type	Required	Notes
`name`	text	Yes	Action Title. Placeholder: Brief summary of the action item.
`status`	singleselect		Status.
`priority`	singleselect		Priority.
`assigned_to`	reference → user	Yes	Assigned To.
`due_date`	date		Due Date.
`completed_date`	date		Completed Date.

General: Description

Field	Type	Required	Notes
`description`	text (multi-line)		Describe the action, context, and objectives.
`updates`	text (multi-line)		Log progress notes or outcomes as the action progresses.

General: Linkages

Field	Type	Notes
`meeting`	reference → `MEETING`	Originating Meeting.
`decision`	reference → `DECISION`	Related Decision.
`project`	reference → `PROJECT`	Project.

Attachments

Field	Panel	Allowed types	Max files
`attachments`	Attachments	`.pdf`, `.doc`, `.docx`, `.xls`, `.xlsx`, `.png`, `.jpg`	multiple

Relationships

Lookups: meeting points at a MEETING record; decision points at a DECISION record; project points at a PROJECT record.

Creating a Action via the API

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

{
  "entity":   "ACTION",
  "level":    540,
  "comboKey": "SUB:<your-sub-id>|ENT:",
  "name": "Action Title",
  "assigned_to": "",
  "description": "Description",
  "updates": "Progress Updates"
}

Listing Actions records

GET /v1/entities/ACTION/SUB

DemandFlow Support Centre

ACTION: Action

ACTION: Action

Entity properties

Use cases

Fields

Attachments

Relationships

Creating a Action via the API

Listing Actions records

See also

Was this article helpful?