Rack bays and floor spaces
19 declared fields for Floor space. Required fields include Floor plan, Name.
Demo baseline · November 13, 2026About 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_layout_spaces- Record label
- Floor space
Field definitions
| Field | Type or reference | Built-in rules | Choices and constraints |
|---|---|---|---|
Floor planplanId | reference dc_floor_plans | Required Default list field | — |
Namename | text | Required Default list field | — |
Space typekind | select | Default list field | rack_bay, cage, aisle, utility, obstruction, door, power_equipment, cooling_equipment, security_equipment, other_equipment |
X coordinate (m)x | number | Optional by default | Minimum 0 |
Y coordinate (m)y | number | Optional by default | Minimum 0 |
Width (m)widthM | number | Optional by default | Minimum 0.1 |
Depth (m)depthM | number | Optional by default | Minimum 0.1 |
Availabilitystatus | select | Default list field | available, occupied, reserved, unavailable |
Rotation (0 or 90)rotation | number | Optional by default | Minimum 0 |
Rack CIrackCiId | reference__cmdb | Default list field | — |
Allocated customeraccountId | reference customer_accounts | Default list field | — |
Facility equipment CIequipmentCiId | reference__cmdb | Default list field | — |
Measured object height (m)heightM | number | Optional by default | Minimum 0.01 |
Rated bay power (kW)capacityKw | number | Optional by default | Minimum 0 |
Reservation expiryreservationExpires | datetime-local | Optional by default | — |
Activeactive | boolean | Default list field | — |
Demo datasetdemoDataset | text | Read-only Default list field | — |
CreatedcreatedAt | text | Read-only | — |
UpdatedupdatedAt | text | Read-only | — |
Lifecycle values
These are stored values from the form definition. Workflow actions can apply additional prerequisites, approvals, and side effects. The workflow determines which transitions are allowed.
| Field | Values |
|---|---|
| Availability | available, occupied, reserved, unavailable |
Find the procedure and verify the outcome
Verification evidence
The disposable audit exercised 20 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.
| Role | HTTP status |
|---|---|
| Asset Manager | 403 |
| Change Manager | 403 |
| CMDB Manager | 403 |
| Contract manager | 403 |
| Customer service agent | 403 |
| Customer service customer | 403 |
| Customer service manager | 403 |
| Datacenter Customer | 403 |
| Datacenter Fulfiller | 403 |
| Datacenter Manager | 200 |
| Datacenter Vendor | 403 |
| EH&S auditor | 403 |
| EH&S manager | 403 |
| Executive Reader | 403 |
| Field service dispatcher | 403 |
| Field service technician | 403 |
| HR case agent | 403 |
| HR knowledge manager | 403 |
| HR lifecycle manager | 403 |
| HR profile manager | 403 |
| Employee Relations investigator | 403 |
| HR service catalog administrator | 403 |
| Inventory Counter | 403 |
| ITIL Fulfiller | 403 |
| Knowledge Manager | 403 |
| Business Manager | 403 |
| Platform Administrator | 200 |
| Service Desk Agent | 403 |
| Vendor manager | 403 |
| Third-party risk manager | 403 |
| Employee with no workspace role | 403 |
Edit and verify
- Open the list from the appropriate workspace and select an existing record or a permitted create action. Confirm the intended tenant and record number.
- 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.
- 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.