Vendor accounts
20 declared fields for Vendor account. Required fields include Name, Vendor code.
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
vendor_accounts- Record label
- Vendor account
Field definitions
| Field | Type or reference | Built-in rules | Choices and constraints |
|---|---|---|---|
Namename | text | Required Default list field | — |
Vendor codecode | text | Required Default list field | — |
CompanycompanyId | reference companies | Default list field | — |
Primary contactprimaryContactId | reference users | Default list field | — |
Qualificationstatus | select | Default list field | onboarding, approved, suspended, expired |
Qualified service categoriesserviceCategories | tag_list | Optional by default | Use the standard datacenter categories: hardware, network, storage, power, cooling, environment, security, cabling, remote_hands, capacity, compliance |
Support emailsupportEmail | Optional by default | — | |
Dispatch phonephone | text | Optional by default | — |
Escalation contactescalationContact | text | Optional by default | — |
Insurance expiryinsuranceExpires | date | Optional by default | — |
Certification expirycertificationExpires | date | Optional by default | — |
Currencycurrency | text | Optional by default | — |
Descriptiondescription | textarea | Optional by default | — |
Activeactive | boolean | Default list field | — |
Demo datasetdemoDataset | text | Read-only Default list field | — |
CreatedcreatedAt | text | Read-only | — |
UpdatedupdatedAt | text | Read-only | — |
LifecyclelifecycleState | text | Read-only Default list field | — |
Business ownerbusinessOwnerId | text users | Read-only | — |
Risk review neededlegacyReviewRequired | text | Read-only Default list field | — |
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 |
|---|---|
| Qualification | onboarding, approved, suspended, expired |
Find the procedure and verify the outcome
Verification evidence
The disposable audit exercised 8 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 | 403 |
| 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.