Qintorava DocsProduct documentation
Form reference

SAM license allocations

21 declared fields for License allocation. Required fields include Entitlement, Software product, Allocated to, Quantity.

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
software_allocations
Record label
License allocation

Field definitions

FieldType or referenceBuilt-in rulesChoices and constraints
Allocation number
allocationNumber		textRead-only
Default list field		—
Entitlement
entitlementId		reference
software_entitlements		Required
Default list field		—
Software product
productId		reference
software_products		Required
Default list field		—
Allocated to
allocatedToType		selectRequireduser, device, department, site
User
userId		reference
users		Optional by default—
Device / CI
ciId		reference
__cmdb		Optional by default—
Department
departmentId		reference
departments		Optional by default—
Site
locationId		reference
locations		Optional by default—
Quantity
quantity		numberRequiredMinimum 1
Allocation state
state		selectRequired
Default list field		requested, approved, allocated, reclamation_requested, reclaimed, cancelled
Allocated
allocatedAt		datetime-localOptional by default—
Reclamation reason
reclamationReason		textOptional by default—
Scheduled reclaim
reclaimScheduledAt		datetime-localOptional by default—
Reclaimed
reclaimedAt		datetime-localOptional by default—
Requested by
requestedById		reference
users		Optional by default—
Approved by
approvedById		reference
users		Optional by default—
Active
active		booleanDefault list field—
Created
createdAt		textRead-only—
Updated
updatedAt		textRead-only—
Demo record key
demoKey		textHidden by defaultStable identifier used by the idempotent demo fixture loader.
Demo dataset
demoDataset		textHidden by defaultSynthetic 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.

FieldValues
Allocation staterequested, approved, allocated, reclamation_requested, reclaimed, cancelled

Related procedure: Allocate software and verify fulfillment.

Verification evidence

The disposable audit exercised 13 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 Manager200
Change Manager200
CMDB Manager403
Contract manager200
Customer service agent200
Customer service customer403
Customer service manager200
Datacenter Customer403
Datacenter Fulfiller200
Datacenter Manager200
Datacenter Vendor403
EH&S auditor403
EH&S manager403
Executive Reader200
Field service dispatcher200
Field service technician200
HR case agent403
HR knowledge manager403
HR lifecycle manager403
HR profile manager403
Employee Relations investigator403
HR service catalog administrator403
Inventory Counter403
ITIL Fulfiller403
Knowledge Manager200
Business Manager200
Platform Administrator200
Service Desk Agent200
Vendor manager200
Third-party risk manager200
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.