SVCCAT: Service Catalog Item
IT service catalog entry describing a standard service offering with delivery details, cost, approval requirements, and ownership. Used to create pre-filled service request tickets.
SVCCAT 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 SVCCAT.Entity properties
| Property | Value |
|---|---|
| Entity code | SVCCAT |
| Display name | Service Catalog Item |
| Plural | Service Catalog |
| Level | 50600 |
Use cases
IT service catalog entry describing a standard service offering with delivery details, cost, approval requirements, and ownership. Used to create pre-filled service request tickets.
SVCCAT defines the catalog of IT services available to users. Each entry describes what the service is, how long it takes, what it costs, and who owns it. The Request Service toolbar button creates a TICKET with ticketType Service Request and links back via serviceCatalogItem. The Related Tickets panel uses stockRecord on serviceCatalogItem to show all tickets raised against this catalog item. Status tracks whether the service is actively offered (Active), being drafted (Draft), or no longer available (Retired).
Fields
Service Information
| Field | Type | Required | Notes |
|---|---|---|---|
ref | text | Ref. Read only. | |
name | text | Yes | Name. |
svcId | text | Yes | Service ID. |
description | text (multi-line) | Yes | Description. |
category | enum | Yes | Valid ids: 1 (Hardware), 2 (Software), 3 (Network), 4 (Access & Permissions), 5 (Communication), 6 (Facilities), 7 (Other). |
status | enum | Yes | Valid ids: 1 (Active), 2 (Draft), 3 (Retired). |
icon | text (FA icon class) | Icon. |
Delivery & Cost
| Field | Type | Required | Notes |
|---|---|---|---|
deliveryTime | text | Delivery Time. | |
cost | number | Cost. | |
approvalRequired | enum | Valid ids: 1 (Yes), 0 (No). | |
approverSource | enum | Valid ids: manager (Requester's line manager), owner (Service owner), named (Named user). | |
approverUser | reference → user | Named approver. | |
supportLevel | reference → SUPLEVEL | Support Level. |
Ownership
| Field | Type | Required | Notes |
|---|---|---|---|
serviceOwner | reference → user | Service Owner. | |
supportGroup | text | Support Group. | |
provider | enum | Valid ids: 1 (Internal), 2 (External), 3 (Hybrid). |
Attachments and additional panels
- Activity timeline panel attached.
Relationships
- Lookups:
supportLevelpoints at aSUPLEVELrecord. - Related lists:
SVCREQvia stockRecord.
Creating a Service Catalog Item via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "SVCCAT",
"level": 50600,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example name",
"svcId": "Example svcId",
"description": "Example text",
"category": 1
}Listing Service Catalog
GET /v1/entities/SVCCAT/SUB