Typed RFQ custom fields
Govern immutable typed metadata definitions for the fixed Procurement RFQ draft-creation consumer, including safe applicability, role visibility and exact transaction snapshots.
Screen orientation
Tenant administrators author and independently publish field sets. Operational preview/capture remains role, site, classification and exact field-visibility scoped.
The field-set editor defines identity and typed ordered fields, bounds and safe conditions. Simulation, independent publication and immutable history appear below.
Field reference
The entries below describe the current screen controls and read-only values. They do not relax server-side validation, site scope, classification handling or required independence in a governed decision.
| Field or value | Control | Required or shown when | How to use or read it | Result |
|---|---|---|---|---|
| Field-set key · Field-set name · Purpose | Text | Required. | Create a stable bounded identity for RFQ metadata. | Forms the immutable field-set register. |
| Stable key · Label · Type · Display order | Field controls | Required per field. | Define a unique key, user label, one supported type and deterministic order. | Creates the exact definition snapshot. |
| Classification | Select | Required. | Set the field's handling level. | Filters preview, display and search by clearance. |
| Help text | Long text | Required. | Explain how the RFQ author should use the field. | Provides retained field guidance. |
| Minimum length · Maximum length | Numeric bounds | Required for bounded text as applicable. | Set safe validation limits; long text cannot be searchable. | Controls text normalization/validation. |
| Minimum · Maximum · Decimal scale | Numeric bounds | Required for integer/decimal as applicable. | Set exact permitted range and decimal precision. | Controls typed numeric normalization. |
| Earliest date · Latest date | Date bounds | Required for bounded date as applicable. | Set the permitted date interval. | Controls typed date validation. |
| Effective from · Change reason | Version controls | Required for publication/replacement. | Set effectivity and explain the immutable successor. | Preserves existing transaction snapshots. |
| Currency · Ownership · Classification · Project reference · Contract reference · Line count | Simulation facts | Required according to field applicability. | Use only the fixed RFQ-known fact catalogue. | Resolves applicable keys without creating an RFQ snapshot. |
| Simulation note | Long text | Required. | Explain the safe scenario being tested. | Stores privacy-minimised simulation evidence. |
Actions and effects
When to use: After the complete typed definition.
What it does: Checks types, bounds, roles, conditions and exact checksum without storing raw transaction values.
When to use: After a successful current-checksum simulation.
What it does: Freezes the field-set version for independent review.
When to use: By a different Tenant Administrator.
What it does: Controls future RFQ selection while existing snapshots remain pinned.
Lists and states
- Field set register: use status, exact version and accountable actors to distinguish current work from retained history.
- History and evidence: hashes and source/version references identify the immutable facts used by each decision.
Authority boundary
Custom fields are display/search metadata for one fixed consumer. They cannot execute scripts/SQL/callbacks, change RFQ/procurement state, post inventory or become a generic form/workflow engine.