Qintorava DocsProduct documentation
Form reference

Preventive maintenance schedules

16 declared fields for Maintenance schedule. Required fields include Name, Published work plan, Location, First occurrence (UTC).

Demo baseline · November 13, 2026
Download PDF

About this form

Use this reference to identify built-in form labels, data types, and validation. Specialized workspaces can render a subset of these fields or provide workflow-specific controls. Your role, record state and tenant configuration can change what you see.

Registry key
dc_maintenance_schedules
Record label
Maintenance schedule

Field definitions

FieldType or referenceBuilt-in rulesChoices and constraints
Name
name		textRequired
Default list field		—
Published work plan
planId		reference
dc_work_plans		Required
Default list field		—
Location
locationId		reference
locations		Required
Default list field		—
Target CI
ciId		reference
__cmdb		Default list field—
Customer account
accountId		reference
customer_accounts		Default list field—
Recurrence
cadence		selectDefault list fieldweekly, monthly, quarterly, yearly
First occurrence (UTC)
anchorAt		datetime-localRequiredEnter UTC time. Recurrence stays anchored in UTC, including across daylight saving changes. Edits affect new occurrences; existing orders retain their approved windows.
Service window (minutes)
durationMinutes		numberOptional by defaultMinimum 15
Last generation attempt
lastGenerationAt		datetime-localRead-only—
Last successful generation
lastSuccessAt		datetime-localRead-only—
Generation error
lastGenerationError		textRead-only
Default list field		—
Next calendar generation
nextGenerationAt		datetime-localRead-only—
Active
active		booleanDefault list field—
Demo dataset
demoDataset		textRead-only
Default list field		—
Created
createdAt		textRead-only—
Updated
updatedAt		textRead-only—

Verification evidence

The disposable audit exercised 9 applicable validation assertions on this definition. The authenticated collection read returned HTTP 200. See the verification matrix for scope.

Collection read results by built-in role

These statuses were observed over HTTP with one role per disposable MFA account. A successful list response can be empty and does not establish individual record, field, or write access.

RoleHTTP status
Asset Manager403
Change Manager403
CMDB Manager403
Contract manager403
Customer service agent403
Customer service customer403
Customer service manager403
Datacenter Customer403
Datacenter Fulfiller403
Datacenter Manager200
Datacenter Vendor403
EH&S auditor403
EH&S manager403
Executive Reader403
Field service dispatcher403
Field service technician403
HR case agent403
HR knowledge manager403
HR lifecycle manager403
HR profile manager403
Employee Relations investigator403
HR service catalog administrator403
Inventory Counter403
ITIL Fulfiller403
Knowledge Manager403
Business Manager403
Platform Administrator200
Service Desk Agent403
Vendor manager403
Third-party risk manager403
Employee with no workspace role403

Edit and verify

  1. Open the list from the appropriate workspace and select an existing record or a permitted create action. Confirm the intended tenant and record number.
  2. Use the visible controls for the current record type and state. For reference fields, select a returned record from the lookup. Fill visible required fields and use the dedicated workflow action when the record has approval or completion gates.
  3. After saving, reopen the record and compare its persisted values, state and activity to the intended change. Check the downstream linked record when the action creates one.

Troubleshoot

  • Missing field or control: compare the role, module, record state, form conditions and tenant overrides.
  • Lookup returns no result: check that the referenced record is active, in scope and compatible with the current field.
  • Save is rejected: keep the exact validation message and compare the field key, choice, constraints and required related records.
  • See Edit and troubleshoot records and Configuration Studio.