Form reference

Hardware CI lifecycle workflows

37 declared fields for Hardware CI lifecycle workflow. Required fields include Lifecycle flow, Workflow state, Requested by, Effective date.

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: hardware_asset_transactions
Record label: Hardware CI lifecycle workflow

Field definitions

Field	Type or reference	Built-in rules	Choices and constraints
Transaction number `number`	text	Read-only Default list field	—
Approved hardware request `assetRequestId`	reference asset_requests	Read-only	—
Lifecycle flow `flowType`	select	Required Default list field	`procurement`, `allocation`, `transfer`, `decommission`, `lease`, `disposal`, `reclamation`
Workflow state `state`	select	Required Default list field	`draft`, `requested`, `approved`, `in_progress`, `complete`, `cancelled`
CMDB asset record `assetId`	reference hardware_assets	Default list field	—
Configuration item `ciId`	reference `__cmdb`	Read-only Default list field	—
Requested by `requestedById`	reference users	Required	—
Approved by `approvedById`	reference users	Optional by default	—
Effective date `effectiveAt`	datetime-local	Required Default list field	—
Vendor `vendor`	text	Optional by default	Asset flows `procurement`
Purchase order `purchaseOrder`	text	Optional by default	Asset flows `procurement`
Quantity `quantity`	number	Optional by default	Minimum `1` Asset flows `procurement`
Unit cost `unitCost`	number	Optional by default	Minimum `0` Asset flows `procurement`
Expected delivery `expectedDelivery`	date	Optional by default	Asset flows `procurement`
Allocate to user `assignedUserId`	reference users	Optional by default	Asset flows `allocation, reclamation`
Department `assignedDepartmentId`	reference departments	Optional by default	Asset flows `allocation`
Target location `targetLocationId`	reference locations	Optional by default	Asset flows `allocation, transfer`
Source stockroom `sourceStockroomId`	reference stockrooms	Optional by default	Asset flows `allocation, transfer`
Destination stockroom `destinationStockroomId`	reference stockrooms	Optional by default	Asset flows `transfer, reclamation`
Lessor `lessor`	text	Optional by default	Asset flows `lease`
Lease contract `leaseContract`	text	Optional by default	Asset flows `lease`
Lease start `leaseStart`	date	Optional by default	Asset flows `lease`
Lease end `leaseEnd`	date	Optional by default	Asset flows `lease`
Renewal option `renewalOption`	select	Optional by default	`renew`, `return`, `purchase` Asset flows `lease`
Decommission reason `decommissionReason`	textarea	Optional by default	Asset flows `decommission`
Data sanitization method `dataSanitizationMethod`	select	Optional by default	`cryptographic_erase`, `secure_wipe`, `physical_destruction`, `not_applicable` Asset flows `decommission, disposal`
Disposal method `disposalMethod`	select	Optional by default	`certified_recycler`, `resale`, `donation`, `return_to_vendor`, `destruction` Asset flows `disposal`
Disposal vendor `disposalVendor`	text	Optional by default	Asset flows `disposal`
Disposal certificate URL `disposalCertificate`	url	Optional by default	Asset flows `disposal`
Reclamation reason `reclamationReason`	select	Optional by default	`offboarding`, `refresh`, `unused`, `policy`, `repair` Asset flows `reclamation`
Condition on return `conditionOnReturn`	select	Optional by default	`good`, `fair`, `damaged`, `unusable` Asset flows `reclamation`
Workflow notes `workNotes`	textarea	Optional by default	—
Active `active`	boolean	Default list field	—
Created `createdAt`	text	Read-only	—
Updated `updatedAt`	text	Read-only	—
Demo record key `demoKey`	text	Hidden by default	Stable identifier used by the idempotent demo fixture loader.
Demo dataset `demoDataset`	text	Hidden by default	Synthetic demonstration records. Not actual organizational inventory, financials or execution evidence.

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
Workflow state	`draft`, `requested`, `approved`, `in_progress`, `complete`, `cancelled`

Related procedure: Request and provision hardware.

Verification evidence

The disposable audit exercised 21 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	200
Change Manager	200
CMDB Manager	403
Contract manager	200
Customer service agent	200
Customer service customer	403
Customer service manager	200
Datacenter Customer	403
Datacenter Fulfiller	200
Datacenter Manager	200
Datacenter Vendor	403
EH&S auditor	403
EH&S manager	403
Executive Reader	200
Field service dispatcher	200
Field service technician	200
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	200
Business Manager	200
Platform Administrator	200
Service Desk Agent	200
Vendor manager	200
Third-party risk manager	200
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.