FDREQUEST: Front Door Request
Log of submissions made through front doors, tracking what was created and by whom.
Default definition. This article describes the default
FDREQUEST 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 FDREQUEST.Entity properties
| Property | Value |
|---|---|
| Entity code | FDREQUEST |
| Display name | Front Door Request |
| Plural | Front Door Requests |
| Level | 50300 |
Use cases
FDREQUEST is an audit log entity at level 50300. The General panel uses a 50/50 split: left column shows readonly request details (title, front door name, door type as Simple/Complex, submitted datetime, submitted by user); right column has a readonly objectarray of created items showing entity, target name, object name, and ID with click-through enabled. All fields are readonly as this is a system-generated record.
Fields
Request Details
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Title. Read only. | |
doorName | text | Front Door. Read only. | |
doorType | enum | Valid ids: 1 (Simple), 2 (Complex). | |
created | datetime | Submitted. Read only. | |
ownerId | reference → user | Submitted By. Read only. |
Embedded arrays
| Field | Type | Required | Notes |
|---|---|---|---|
createdObjects | array | Each entry has: entity, targetName, objectName, objectId. |
Relationships
- No declared relationships in the default definition.
Creating a Front Door Request via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "FDREQUEST",
"level": 50300,
"comboKey": "SUB:<your-sub-id>|ENT:"
}Listing Front Door Requests records
GET /v1/entities/FDREQUEST/SUB:<your-sub-id>