SVCREQ: Service Request
A request raised by a user for a service from the IT service catalogue. Tracks the request from submission through approval, fulfilment, and closure.
Default definition. This article describes the default
SVCREQ 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 SVCREQ.Entity properties
| Property | Value |
|---|---|
| Entity code | SVCREQ |
| Display name | Service Request |
| Plural | Service Requests |
| Level | 50650 |
Use cases
A request raised by a user for a service from the IT service catalogue. Tracks the request from submission through approval, fulfilment, and closure.
Fields
Request Information
| Field | Type | Required | Notes |
|---|---|---|---|
ref | text | Request ref.. Read only. | |
name | text | Yes | Subject. |
description | text (multi-line) | Description. | |
requestData | text (multi-line) | JSON of the custom fields captured when this request was submitted from the service catalogue. Read only. | |
status | enum | Yes | Valid ids: 1 (New), 2 (Approved), 3 (In Progress), 4 (Pending), 5 (Fulfilled), 6 (Closed), 7 (Rejected), 8 (Cancelled). |
Classification
| Field | Type | Required | Notes |
|---|---|---|---|
serviceCatalogItem | reference → SVCCAT | Catalogue Item. | |
category | enum | Valid ids: 1 (Hardware), 2 (Software), 3 (Network), 4 (Access & Permissions), 5 (Communication), 6 (Facilities), 7 (Other). | |
priority | enum | Yes | Valid ids: 1 (Critical), 2 (High), 3 (Medium), 4 (Low). |
People
| Field | Type | Required | Notes |
|---|---|---|---|
requestedBy | reference → user | Requested By. Read only. | |
requestedFor | reference → user | If requesting on behalf of someone else | |
assignedTo | reference → user | Assigned To. | |
assignedGroup | text | Assigned Group. |
Approval
| Field | Type | Required | Notes |
|---|---|---|---|
approvalRequired | enum | Valid ids: 1 (Yes), 0 (No). | |
approvedBy | reference → user | Approved By. | |
approvalDate | datetime | Approval Date. | |
rejectionReason | text (multi-line) | Rejection Reason. |
Fulfilment Details
| Field | Type | Required | Notes |
|---|---|---|---|
expectedDelivery | date | Expected Delivery. | |
fulfilledDate | datetime | Fulfilled Date. | |
closedDate | datetime | Closed Date. | |
fulfilmentNotes | text (multi-line) | Fulfilment Notes. | |
satisfactionRating | enum | Valid ids: 5 (Very Satisfied), 4 (Satisfied), 3 (Neutral), 2 (Dissatisfied), 1 (Very Dissatisfied). |
Attachments and additional panels
- Activity timeline panel attached.
Relationships
- Lookups:
serviceCatalogItempoints at aSVCCATrecord. - Related lists:
SVCAPPROVALvia stockRecord.
Creating a Service Request via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "SVCREQ",
"level": 50650,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example name",
"status": 1,
"priority": 1
}Listing Service Requests
GET /v1/entities/SVCREQ/SUB