ITSVC: IT Service
A business-level IT service (e.g. Email, DNS, VPN, CRM) that groups infrastructure, change requests, tickets, and problems for impact analysis and service health tracking.
Default definition. This article describes the default
ITSVC 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 ITSVC.Entity properties
| Property | Value |
|---|---|
| Entity code | ITSVC |
| Display name | IT Service |
| Plural | IT Services |
| Level | 50550 |
Use cases
ITSVC sits between SVCCAT (user-facing catalog items) and SVC (device-level network services). It represents the logical IT service that users consume. ITCHANGE, TICKET, ITPROBLEM, and CMDB all reference ITSVC via a service objectLookup field, and the relatedlist panels here use stockRecord on that field to show all linked records.
Fields
Service Information
| Field | Type | Required | Notes |
|---|---|---|---|
ref | text | Ref. | |
name | text | Yes | Service Name. |
serviceId | text | Service ID. | |
description | text (multi-line) | Description. | |
serviceType | enum | Valid ids: 1 (Internal), 2 (External), 3 (Hybrid). | |
status | enum | Yes | Valid ids: 1 (Operational), 2 (Degraded), 3 (Partial Outage), 4 (Major Outage), 5 (Planned), 6 (Under Maintenance), 7 (Retired). |
category | enum | Valid ids: 1 (Infrastructure), 2 (Communication), 3 (Business Application), 4 (Security), 5 (Cloud), 6 (Platform), 7 (Other). |
Classification
| Field | Type | Required | Notes |
|---|---|---|---|
criticality | enum | Valid ids: 1 (Business Critical), 2 (Important), 3 (Standard), 4 (Low). | |
environment | enum | Valid ids: 1 (Production), 2 (Staging), 3 (Development), 4 (DR). | |
vendor | reference → VEN | Vendor. |
Ownership
| Field | Type | Required | Notes |
|---|---|---|---|
serviceOwner | reference → user | Service Owner. | |
supportGroup | text | Support Group. | |
supportLevel | reference → SUPLEVEL | Support Level. | |
department | reference → DEPT | Department. | |
supportAgreement | reference → SUPAGREEMENT | Support Agreement. |
SLA Targets
| Field | Type | Required | Notes |
|---|---|---|---|
availabilityTarget | text | Availability Target. | |
rtoMinutes | number | Recovery Time Objective | |
rpoMinutes | number | Recovery Point Objective |
Support Details
| Field | Type | Required | Notes |
|---|---|---|---|
supportHours | text | Support Hours. | |
escalationContact | reference → user | Escalation Contact. | |
maxDowntimeMinutes | number | Maximum acceptable downtime per incident |
Additional panels
- Activity timeline panel attached.
Relationships
- Lookups:
vendorpoints at aVENrecord;supportLevelpoints at aSUPLEVELrecord;departmentpoints at aDEPTrecord;supportAgreementpoints at aSUPAGREEMENTrecord;serviceOwnerpoints at a user;escalationContactpoints at a user. - Related lists:
CMDB,ITCHANGE,TICKET,ITPROBLEM.
Creating a IT Service via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "ITSVC",
"level": 50550,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example",
"status": "1",
"ref": "...",
"serviceId": "..."
}Listing IT Services
# All records in your tenant
GET /v1/entities/ITSVC/SUB:<your-sub-id>